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

Temporal

Extends:

TemporalAccessor → Temporal

Direct Subclass:

ChronoLocalDate, ChronoLocalDateTime, ChronoZonedDateTime, Instant, LocalTime, OffsetDateTime, OffsetTime, packages/core/src/format/DateTimeParseContext.js~Parsed, Year, YearMonth

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 fields (see TemporalField) or queries (see TemporalQuery). 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 TemporalField with the number held using a 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 Chronology and the ZoneId. These can be accessed 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 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 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:

  • 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.
  • 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.
  • 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.

Method Summary

Public Methods
public

isSupported(fieldOrUnit: TemporalUnit): boolean

Checks if the specified unit is supported.
public

minus(amount: TemporalAmount | number, unit: TemporalUnit): Temporal

function overloading for Temporal.plus
public

plus(amount: TemporalAmount | number, unit: TemporalUnit): Temporal

function overloading for Temporal.plus
public

until(endTemporal: Temporal, unit: TemporalUnit): number

Calculates the period between this temporal and another temporal in terms of the specified unit.
public

with(adjusterOrField: TemporalAdjuster | TemporalField, newValue: number): Temporal

function overloading for Temporal.with

Inherited Summary

From class TemporalAccessor
public

get(field: TemporalField): number

Gets the value of the specified field as an int.
public

getLong(field: *)

public

isSupported(field: *)

public

query(query: TemporalQuery): *

Queries this date-time.
public

Gets the range of valid values for the specified field.

Public Methods

public isSupported(fieldOrUnit: TemporalUnit): boolean source

Checks if the specified unit is supported. This checks if the date-time can be queried for the specified unit. If false, then calling the plus and minus methods will throw an exception.

Specification for implementors

Implementations must check and handle all fields defined in ChronoUnit. If the field is supported, then true is returned, otherwise false If the field is not a ChronoUnit, then the result of this method is obtained by invoking TemporalUnit.isSupportedBy(Temporal) passing this as the argument.

Implementations must not alter this object.

Override:

TemporalAccessor#isSupported

Params:

NameTypeAttributeDescription
fieldOrUnit TemporalUnit

the unit to check, null returns false

Return:

boolean

true if this date-time can be queried for the unit, false if not

public minus(amount: TemporalAmount | number, unit: TemporalUnit): Temporal source

function overloading for Temporal.plus

Called with 1 (or less) arguments, p1 is expected to be a TemporalAmount and Temporal.minusAmount is called.

Otherwise Temporal.minusAmountUnit is called.

Params:

NameTypeAttributeDescription
amount TemporalAmount | number
  • nullable: false
unit TemporalUnit

Return:

Temporal

public plus(amount: TemporalAmount | number, unit: TemporalUnit): Temporal source

function overloading for Temporal.plus

Called with 1 (or less) arguments, p1 is expected to be a TemporalAmount and Temporal.plusAmount is called.

Otherwise Temporal.plusAmountUnit is called.

Params:

NameTypeAttributeDescription
amount TemporalAmount | number
  • nullable: false
unit TemporalUnit

Return:

Temporal

public until(endTemporal: Temporal, unit: TemporalUnit): number source

Calculates the period between this temporal and another temporal in terms of the specified unit. This calculates the period between two temporals in terms of a single unit. The start and end points are this and the specified temporal. The result will be negative if the end is before the start. For example, the period in hours between two temporal objects can be calculated using startTime.until(endTime, HOURS).

The calculation returns a whole number, representing the number of complete units between the two temporals. For example, the period in hours between the times 11:30 and 13:29 will only be one hour as it is one minute short of two hours.

There are two equivalent ways of using this method. The first is to invoke this method directly. The second is to use TemporalUnit.between(Temporal, Temporal):

   // these two lines are equivalent
   between = thisUnit.between(start, end);
   between = start.until(end, thisUnit);

The choice should be made based on which makes the code more readable. For example, this method allows the number of days between two dates to be calculated:

   long daysBetween = DAYS.between(start, end);
   // or alternatively
   long daysBetween = start.until(end, DAYS);

Specification for implementors

Implementations must begin by checking to ensure that the input temporal object is of the same observable type as the implementation. They must then perform the calculation for all instances of ChronoUnit. A DateTimeException must be thrown for ChronoUnit instances that are unsupported. If the unit is not a ChronoUnit, then the result of this method is obtained by invoking TemporalUnit.between(Temporal, Temporal) passing this as the first argument and the input temporal as the second argument.

In summary, implementations must behave in a manner equivalent to this code:

  // check input temporal is the same type as this class
  if (unit instanceof ChronoUnit) {
    // if unit is supported, then calculate and return result
    // else throw DateTimeException for unsupported units
  }
  return unit.between(this, endTemporal);

The target object must not be altered by this method.

Params:

NameTypeAttributeDescription
endTemporal Temporal

the end temporal, of the same type as this object, not null
unit TemporalUnit

the unit to measure the period in, not null

Return:

number

the amount of the period between this and the end

Throw:

*

DateTimeException - if the period cannot be calculated

*

ArithmeticException - if numeric overflow occurs

public with(adjusterOrField: TemporalAdjuster | TemporalField, newValue: number): Temporal source

function overloading for Temporal.with

Called with 1 (or less) arguments, p1 is expected to be a TemporalAdjuster and Temporal.withAdjuster is called.

Otherwise Temporal.withFieldValue is called.

Params:

NameTypeAttributeDescription
adjusterOrField TemporalAdjuster | TemporalField
  • nullable: false
newValue number

Return:

Temporal