Temporal.PlainDate.prototype.toZonedDateTime()
Limited availability
This feature is not Baseline because it does not work in some of the most widely-used browsers.
Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The toZonedDateTime() method of Temporal.PlainDate instances returns a new Temporal.ZonedDateTime object representing this date, a supplied time, and a supplied time zone, in the same calendar system.
Syntax
toZonedDateTime(timeZone)
toZonedDateTime(info)
Parameters
timeZone-
Either a string or a
Temporal.ZonedDateTimeinstance representing thetimeZoneoption. This is a convenience overload, sotoZonedDateTime(timeZone)is equivalent totoZonedDateTime({ timeZone }), wheretimeZoneis a string orTemporal.ZonedDateTime. This overload is chosen when the first argument is not an object, or the object'stimeZoneproperty isundefined(becauseZonedDateTimeinstances have atimeZoneIdproperty instead). info-
An object containing some or all of the following properties (in the order they are retrieved and validated):
plainTimeOptional-
A string, an object, or a
Temporal.PlainTimeinstance representing the time component of the resultingZonedDateTime. It is converted to aTemporal.PlainTimeobject using the same algorithm asTemporal.PlainTime.from(). Defaults to the first valid time in this time zone on this calendar date, which is usually"00:00:00", but may be different if, for example, daylight saving time skips midnight. timeZone-
Either a string or a
Temporal.ZonedDateTimeinstance representing the time zone to use. If aTemporal.ZonedDateTimeinstance, its time zone is used. If a string, it can be a named time zone identifier, an offset time zone identifier, or a date-time string containing a time zone identifier or an offset (see time zones and offsets for more information).
Return value
A new Temporal.ZonedDateTime object representing the date and time specified by this date, plainTime, and timeZone, interpreted in the calendar system of this date.
In the case of ambiguities, the compatible behavior is always used: if the time falls into a gap, we move forward by the gap length; if the time falls into an ambiguity, we choose the earlier of the two possibilities. This means the resulting ZonedDateTime may have a potentially different date or time than the input.
Exceptions
TypeError-
Thrown if
timeZoneis not a string or aTemporal.ZonedDateTimeinstance. RangeError-
Thrown if
timeZoneis a string that is not a valid time zone identifier.
Examples
>Using toZonedDateTime()
const summer = Temporal.PlainDate.from("2021-07-01");
// Just time zone
const summerTime = summer.toZonedDateTime("America/New_York");
console.log(summerTime.toString()); // 2021-07-01T00:00:00-04:00[America/New_York]
const winter = Temporal.PlainDate.from("2021-01-01");
// Time zone and time
const winterTime = winter.toZonedDateTime({
plainTime: "12:34:56",
timeZone: "America/New_York",
});
console.log(winterTime.toString()); // 2021-01-01T12:34:56-05:00[America/New_York]
const spring = Temporal.PlainDate.from("2021-03-01");
// Time zone as object and time as object
const springTime = spring.toZonedDateTime({
plainTime: summerTime.toPlainTime(),
timeZone: winterTime,
});
console.log(springTime.toString()); // 2021-03-01T00:00:00-05:00[America/New_York]
Specifications
| Specification |
|---|
| Temporal> # sec-temporal.plaindate.prototype.tozoneddatetime> |
Browser compatibility
Loading…