This site describes solve-engine as it is on main: 2.43.0, which npm does not have yet. npm installs 2.40.0, so a page may show an answer that version does not give yet.
TemporalZonedDateTimeLike
Defined in: packages/engine/src/temporal/TemporalCalendar.ts:63
The part of a Temporal.ZonedDateTime the backend reads: the calendar
fields (a one-based month and an ISO weekday, Monday 1 to Sunday 7, both
translated at the boundary), the offset, and the instant.
Properties
Section titled “Properties”readonly day: number;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:67
dayOfWeek
Section titled “dayOfWeek”readonly dayOfWeek: number;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:69
ISO weekday: Monday is 1, Sunday is 7.
epochMilliseconds
Section titled “epochMilliseconds”readonly epochMilliseconds: number;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:76
readonly hour: number;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:70
millisecond
Section titled “millisecond”readonly millisecond: number;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:73
minute
Section titled “minute”readonly minute: number;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:71
readonly month: number;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:66
One-based month, 1 is January, as Temporal counts.
offsetNanoseconds
Section titled “offsetNanoseconds”readonly offsetNanoseconds: number;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:75
The zone’s offset from UTC at this instant, in nanoseconds, positive when ahead.
second
Section titled “second”readonly second: number;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:72
timeZoneId
Section titled “timeZoneId”readonly timeZoneId: string;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:78
The zone’s canonical IANA identifier.
readonly year: number;Defined in: packages/engine/src/temporal/TemporalCalendar.ts:64