The cadence half of a Temporal schedule, as it comes back from describe().
Built directly on Temporal's description types rather than a lossy string
re-modeling: calendar fields are Range<number>[] (e.g. hour 17 →
[{ start: 17, end: 17, step: 1 }]), intervals are millisecond numbers. The
UI formats these for display; formatCalendarField below is the bridge. On
read, cron expressions have already been normalized by Temporal into
calendars, so there is no cronExpressions field here.
The cadence half of a Temporal schedule, as it comes back from
describe(). Built directly on Temporal's description types rather than a lossy string re-modeling: calendar fields areRange<number>[](e.g. hour 17 →[{ start: 17, end: 17, step: 1 }]), intervals are millisecond numbers. The UI formats these for display;formatCalendarFieldbelow is the bridge. On read, cron expressions have already been normalized by Temporal intocalendars, so there is nocronExpressionsfield here.