ZonedTime
An instant seen in a zone, written 2026-10-25T09:30:00+00:00[Europe/London].
Time and calendar; not ordered; since Jadpo 0.1.0.
Make one
text.parse(raw, as: ZonedTime) reads one from its text; text that isn't one at all fails malformed, such as 2026-10-25T09:30:00Z or 2026-10-25T09:30:00+00:00.
These operations give one: temporal.add_days, temporal.add_months, temporal.add_years, temporal.in_zone, temporal.occurrences and temporal.resolve.
Text, JSON and storage
text.from writes its canonical text, the one form text.parse reads back. JSON sends an object of its parts.
| Text | JSON |
|---|---|
2026-10-25T09:30:00+00:00[Europe/London] |
{"instant":"2026-10-25T09:30:00Z","zone":"Europe/London"} |
It is stored in 2 columns, each named for the field, _ and its suffix. This is 2026-10-25T09:30:00+00:00[Europe/London]:
| Column | Type | Holds |
|---|---|---|
<field>_instant |
timestamptz(3) |
'2026-10-25 09:30:00.000000+00'::timestamptz |
<field>_zone |
text |
'Europe/London' |
Shown to people
text.format(value, locale:) shows it to people in their locale. A call also gives format:.
With locale: Locale.en_gb and format: TimeFormat.date_time_medium:
| Value | Shown |
|---|---|
2026-10-25T09:30:00+00:00[Europe/London] |
25 Oct 2026, 09:30:00 |
Operations
temporal.add_days(value: T, days: Int, dst: Dst?) -> T:valuemoved by whole calendar days, the clock time kept.temporal.add_months(value: T, months: Int, invalid_day: InvalidDay?, dst: Dst?) -> T:valuemoved by whole calendar months, the day and clock time kept.temporal.add_years(value: T, years: Int, invalid_day: InvalidDay?, dst: Dst?) -> T:valuemoved by whole calendar years, the day and clock time kept.temporal.date(value: ZonedTime) -> CalendarDate: A local time's date.temporal.day(value: T) -> Int: The day of the month, from 1.temporal.format_relative(value: T, now: Instant, zone: Zone?, locale: Locale) -> PresentationText:valueshown to a person inlocaleas how long ago it was fromnow: "just now", minutes, "Today at", "Yesterday at", the weekday, then the long date.temporal.hour(value: ZonedTime) -> Int: A local time's hour, from 0 to 23.temporal.in_zone(instant: Instant, zone: Zone) -> ZonedTime:instantas the local time inzone.temporal.instant(value: ZonedTime) -> Instant: The instant a local time is.temporal.minute(value: ZonedTime) -> Int: A local time's minute, from 0 to 59.temporal.month(value: T) -> Int: The month, from 1 for January.temporal.occurrences(rule: RecurrenceRule, from: T, count: Int) -> List<ZonedTime>: The nextcountoccurrences ofruleat or afterfrom, in its zone (RFC 5545): fewer when the rule ends first;countis from 1 to 1000, so an unbounded rule is never expanded without a bound. From a date, the days they fall on,List<CalendarDate>, which a rule on dates gives; from anInstant, a timed rule's local times.temporal.resolve(date: T, at: Text?, zone: Zone, dst: Dst?) -> ZonedTime: The instant the clock readsatondateinzone, or aLocalDateTimegiven asdatereads with noat:;dst:chooses one in a daylight-saving gap or overlap.temporal.weekday(value: T) -> Weekday: The day of the week.temporal.year(value: T) -> Int: The year of a date or of a local time's date.temporal.zone(value: ZonedTime) -> Zone: The zone a local time is seen in.
Like every standard type, it also has the contract's own operations: text.parse, text.from, text.format, json.read, json.write and ==. It isn't ordered, so < and sorting don't take it. Every standard type meets one contract says how they work.
Markdown for agents: /docs/types/type-zoned-time.md.Built from Jadpo main at e00e61f.