TemporalAccessor
Direct Subclass:
Indirect Subclass:
Method Summary
Public Methods | ||
public |
get(field: TemporalField): number Gets the value of the specified field as an {@code int}. |
|
public |
query(query: TemporalQuery): * Queries this date-time. |
|
public |
range(field: TemporalField): ValueRange Gets the range of valid values for the specified field. |
Public Methods
public get(field: TemporalField): number source
Gets the value of the specified field as an {@code int}.
This queries the date-time for the value for the specified field. The returned value will always be within the valid range of values for the field. If the date-time cannot return the value, because the field is unsupported or for some other reason, an exception will be thrown.
Specification for implementors
Implementations must check and handle all fields defined in ChronoField. If the field is supported and has an {@code int} range, then the value of the field must be returned. If unsupported, then a {@code DateTimeException} must be thrown.If the field is not a {@code ChronoField}, then the result of this method is obtained by invoking {@code TemporalField.getFrom(TemporalAccessor)} passing {@code this} as the argument.
Implementations must not alter either this object.
Params:
Name | Type | Attribute | Description |
field | TemporalField | the field to get, not null |
Throw:
* |
DateTimeException if a value for the field cannot be obtained |
* |
DateTimeException if the range of valid values for the field exceeds an {@code int} |
* |
DateTimeException if the value is outside the range of valid values for the field |
* |
ArithmeticException if numeric overflow occurs |
public query(query: TemporalQuery): * source
Queries this date-time.
This queries this date-time using the specified query strategy object.
Queries are a key tool for extracting information from date-times. They exists to externalize the process of querying, permitting different approaches, as per the strategy design pattern. Examples might be a query that checks if the date is the day before February 29th in a leap year, or calculates the number of days to your next birthday.
The most common query implementations are method references, such as {@code LocalDate::from} and {@code ZoneId::from}. Further implementations are on TemporalQueries. Queries may also be defined by applications.
Params:
Name | Type | Attribute | Description |
query | TemporalQuery | the query to invoke, not null |
Return:
* | the query result, null may be returned (defined by the query) |
Throw:
* |
DateTimeException if unable to query |
* |
ArithmeticException if numeric overflow occurs |
public range(field: TemporalField): ValueRange source
Gets the range of valid values for the specified field.
All fields can be expressed as a {@code long} integer. This method returns an object that describes the valid range for that value. The value of this temporal object is used to enhance the accuracy of the returned range. If the date-time cannot return the range, because the field is unsupported or for some other reason, an exception will be thrown.
Note that the result only describes the minimum and maximum valid values and it is important not to read too much into them. For example, there could be values within the range that are invalid for the field.
Specification for implementors
Implementations must check and handle all fields defined in ChronoField. If the field is supported, then the range of the field must be returned. If unsupported, then a {@code DateTimeException} must be thrown.If the field is not a {@code ChronoField}, then the result of this method is obtained by invoking {@code TemporalField.rangeRefinedBy(TemporalAccessorl)} passing {@code this} as the argument.
Implementations must not alter either this object.
Params:
Name | Type | Attribute | Description |
field | TemporalField | the field to query the range for, not null |
Throw:
* |
DateTimeException if the range for the field cannot be obtained |