A calendar edit changes only what it sends; a new one without a zone takes the member's

Shipped: September 28, 2026 at 8:32 PM UTC
Author: Kamo
Commit: be7db38

The calendar create and edit bound the UserCalendar entity, whose defaults (zone UTC, visible, sort order 0) stood in for every field a body left out. KamoMobile's rename sends {name, color}, so it reset the calendar's zone to UTC, unhid it and moved it first; and a create without a zone was always UTC, never the member's zone. Both now read a CalendarRequest record: a field left out is null and an edit keeps it; a blank zone is none sent (SP98-F-1); an unknown one is 400 INVALID_TIMEZONE; CalendarDto's server-only fields are ignored, so a client can send back what it read. A create sent without an order is still first.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free Forever View Pricing