Home Reference Source Repository 
import {Temporal} from 'js-joda/src/temporal/Temporal.js'
public interface | source

Temporal

Extends:

TemporalAccessor → Temporal

Direct Subclass:

ChronoLocalDate, ChronoLocalDateTime, ChronoZonedDateTime, DateTimeBuilder, DayOfWeek, Instant, LocalTime, Month, src/format/DateTimeParseContext.js~Parsed

Indirect Subclass:

LocalDate, LocalDateTime, ZonedDateTime

Framework-level interface defining read-write access to a temporal object, such as a date, time, offset or some combination of these.

This is the base interface type for date, time and offset objects that are complete enough to be manipulated using plus and minus. It is implemented by those classes that can provide and manipulate information as {@link TemporalField fields} or {@link TemporalQuery queries}. See TemporalAccessor for the read-only version of this interface.

Most date and time information can be represented as a number. These are modeled using {@code TemporalField} with the number held using a {@code long} to handle large values. Year, month and day-of-month are simple examples of fields, but they also include instant and offsets. See ChronoField for the standard set of fields.

Two pieces of date/time information cannot be represented by numbers, the {@link Chronology chronology} and the {@link ZoneId time-zone}. These can be accessed via {@link #query(TemporalQuery) queries} using the static methods defined on TemporalQueries.

This interface is a framework-level interface that should not be widely used in application code. Instead, applications should create and pass around instances of concrete types, such as {@code LocalDate}. There are many reasons for this, part of which is that implementations of this interface may be in calendar systems other than ISO. See ChronoLocalDate for a fuller discussion of the issues.

When to implement

A class should implement this interface if it meets three criteria:

  • it provides access to date/time/offset information, as per {@code TemporalAccessor}

  • the set of fields are contiguous from the largest to the smallest

  • the set of fields are complete, such that no other field is needed to define the valid range of values for the fields that are represented

    Four examples make this clear:

    • {@code LocalDate} implements this interface as it represents a set of fields that are contiguous from days to forever and require no external information to determine the validity of each date. It is therefore able to implement plus/minus correctly.
    • {@code LocalTime} implements this interface as it represents a set of fields that are contiguous from nanos to within days and require no external information to determine validity. It is able to implement plus/minus correctly, by wrapping around the day.
    • {@code MonthDay}, the combination of month-of-year and day-of-month, does not implement this interface. While the combination is contiguous, from days to months within years, the combination does not have sufficient information to define the valid range of values for day-of-month. As such, it is unable to implement plus/minus correctly.

  • The combination day-of-week and day-of-month ("Friday the 13th") should not implement this interface. It does not represent a contiguous set of fields, as days to weeks overlaps days to months.

    • Inherited Summary

    From class TemporalAccessor
    public

    Gets the value of the specified field as an {@code int}.
    public

    query(query: TemporalQuery): *

    Queries this date-time.
    public

    Gets the range of valid values for the specified field.