Added in API level 26

ThaiBuddhistChronology

class ThaiBuddhistChronology : AbstractChronology, Serializable

kotlin.Any
↳	java.time.chrono.AbstractChronology
	↳	java.time.chrono.ThaiBuddhistChronology

The Thai Buddhist calendar system.

This chronology defines the rules of the Thai Buddhist calendar system. This calendar system is primarily used in Thailand. Dates are aligned such that 2484-01-01 (Buddhist) is 1941-01-01 (ISO).

The fields are defined as follows:

era - There are two eras, the current 'Buddhist' (ERA_BE) and the previous era (ERA_BEFORE_BE).
year-of-era - The year-of-era for the current era increases uniformly from the epoch at year one. For the previous era the year increases from one as time goes backwards. The value for the current era is equal to the ISO proleptic-year plus 543.
proleptic-year - The proleptic year is the same as the year-of-era for the current era. For the previous era, years have zero, then negative values. The value is equal to the ISO proleptic-year plus 543.
month-of-year - The ThaiBuddhist month-of-year exactly matches ISO.
day-of-month - The ThaiBuddhist day-of-month exactly matches ISO.
day-of-year - The ThaiBuddhist day-of-year exactly matches ISO.
leap-year - The ThaiBuddhist leap-year pattern exactly matches ISO, such that the two calendars are never out of step.

Summary

Public methods
ThaiBuddhistDate!	`date(prolepticYear: Int, month: Int, dayOfMonth: Int)` Obtains a local date in Thai Buddhist calendar system from the proleptic-year, month-of-year and day-of-month fields.
ThaiBuddhistDate!	`date(era: Era!, yearOfEra: Int, month: Int, dayOfMonth: Int)` Obtains a local date in Thai Buddhist calendar system from the era, year-of-era, month-of-year and day-of-month fields.
ThaiBuddhistDate!	`date(temporal: TemporalAccessor!)` Obtains a local date in this chronology from another temporal object.
ThaiBuddhistDate!	`dateEpochDay(epochDay: Long)` Obtains a local date in the Thai Buddhist calendar system from the epoch-day.
ThaiBuddhistDate!	`dateNow()` Obtains the current local date in this chronology from the system clock in the default time-zone.
ThaiBuddhistDate!	`dateNow(clock: Clock!)` Obtains the current local date in this chronology from the specified clock.
ThaiBuddhistDate!	`dateNow(zone: ZoneId!)` Obtains the current local date in this chronology from the system clock in the specified time-zone.
ThaiBuddhistDate!	`dateYearDay(prolepticYear: Int, dayOfYear: Int)` Obtains a local date in Thai Buddhist calendar system from the proleptic-year and day-of-year fields.
ThaiBuddhistDate!	`dateYearDay(era: Era!, yearOfEra: Int, dayOfYear: Int)` Obtains a local date in Thai Buddhist calendar system from the era, year-of-era and day-of-year fields.
ThaiBuddhistEra!	`eraOf(eraValue: Int)` Creates the chronology era object from the numeric value.
MutableList<Era!>!	`eras()` Gets the list of eras for the chronology.
String!	`getCalendarType()` Gets the calendar type of the underlying calendar system - 'buddhist'.
String!	`getId()` Gets the ID of the chronology - 'ThaiBuddhist'.
Boolean	`isLeapYear(prolepticYear: Long)` Checks if the specified year is a leap year.
ChronoLocalDateTime<ThaiBuddhistDate!>!	`localDateTime(temporal: TemporalAccessor!)` Obtains a local date-time in this chronology from another temporal object.
Int	`prolepticYear(era: Era!, yearOfEra: Int)` Calculates the proleptic-year given the era and year-of-era.
ValueRange!	`range(field: ChronoField!)` Gets the range of valid values for the specified field.
ThaiBuddhistDate!	`resolveDate(fieldValues: MutableMap<TemporalField!, Long!>!, resolverStyle: ResolverStyle!)` Resolves parsed `ChronoField` values into a date during parsing.
ChronoZonedDateTime<ThaiBuddhistDate!>!	`zonedDateTime(instant: Instant!, zone: ZoneId!)` Obtains a `ChronoZonedDateTime` in this chronology from an `Instant`.
ChronoZonedDateTime<ThaiBuddhistDate!>!	`zonedDateTime(temporal: TemporalAccessor!)` Obtains a `ChronoZonedDateTime` in this chronology from another temporal object.

Inherited functions

From class AbstractChronology

`Int`	`compareTo(other: Chronology!)` Compares this chronology to another chronology. The comparison order first by the chronology ID string, then by any additional information specific to the subclass. It is "consistent with equals", as defined by `Comparable`.
`Boolean`	`equals(other: Any?)` Checks if this chronology is equal to another chronology. The comparison is based on the entire state of the object.
`Int`	`hashCode()` A hash code for this chronology. The hash code should be based on the entire state of the object.
`String`	`toString()` Outputs this chronology as a `String`, using the chronology ID.

From class Chronology

`ChronoLocalDate!`	`date(prolepticYear: Int, month: Int, dayOfMonth: Int)` Obtains a local date in this chronology from the proleptic-year, month-of-year and day-of-month fields.
`ChronoLocalDate!`	`date(era: Era!, yearOfEra: Int, month: Int, dayOfMonth: Int)` Obtains a local date in this chronology from the era, year-of-era, month-of-year and day-of-month fields.
`ChronoLocalDate!`	`date(temporal: TemporalAccessor!)` Obtains a local date in this chronology from another temporal object. This obtains a date in this chronology based on the specified temporal. A `TemporalAccessor` represents an arbitrary set of date and time information, which this factory converts to an instance of `ChronoLocalDate`. The conversion typically uses the `EPOCH_DAY` field, which is standardized across calendar systems. This method matches the signature of the functional interface `TemporalQuery` allowing it to be used as a query via method reference, `aChronology::date`.
`ChronoLocalDate!`	`dateEpochDay(epochDay: Long)` Obtains a local date in this chronology from the epoch-day. The definition of `EPOCH_DAY` is the same for all calendar systems, thus it can be used for conversion.
`ChronoLocalDate!`	`dateNow()` Obtains the current local date in this chronology from the system clock in the default time-zone. This will query the `system clock` in the default time-zone to obtain the current date. Using this method will prevent the ability to use an alternate clock for testing because the clock is hard-coded.
`ChronoLocalDate!`	`dateNow(clock: Clock!)` Obtains the current local date in this chronology from the specified clock. This will query the specified clock to obtain the current date - today. Using this method allows the use of an alternate clock for testing. The alternate clock may be introduced using `dependency injection`.
`ChronoLocalDate!`	`dateNow(zone: ZoneId!)` Obtains the current local date in this chronology from the system clock in the specified time-zone. This will query the `system clock` to obtain the current date. Specifying the time-zone avoids dependence on the default time-zone. Using this method will prevent the ability to use an alternate clock for testing because the clock is hard-coded.
`ChronoLocalDate!`	`dateYearDay(prolepticYear: Int, dayOfYear: Int)` Obtains a local date in this chronology from the proleptic-year and day-of-year fields.
`ChronoLocalDate!`	`dateYearDay(era: Era!, yearOfEra: Int, dayOfYear: Int)` Obtains a local date in this chronology from the era, year-of-era and day-of-year fields.
`Long`	`epochSecond(prolepticYear: Int, month: Int, dayOfMonth: Int, hour: Int, minute: Int, second: Int, zoneOffset: ZoneOffset!)` Gets the number of seconds from the epoch of 1970-01-01T00:00:00Z. The number of seconds is calculated using the proleptic-year, month, day-of-month, hour, minute, second, and zoneOffset.
`Long`	`epochSecond(era: Era!, yearOfEra: Int, month: Int, dayOfMonth: Int, hour: Int, minute: Int, second: Int, zoneOffset: ZoneOffset!)` Gets the number of seconds from the epoch of 1970-01-01T00:00:00Z. The number of seconds is calculated using the era, year-of-era, month, day-of-month, hour, minute, second, and zoneOffset.
`Era!`	`eraOf(eraValue: Int)` Creates the chronology era object from the numeric value. The era is, conceptually, the largest division of the time-line. Most calendar systems have a single epoch dividing the time-line into two eras. However, some have multiple eras, such as one for the reign of each leader. The exact meaning is determined by the chronology according to the following constraints. The era in use at 1970-01-01 must have the value 1. Later eras must have sequentially higher values. Earlier eras must have sequentially lower values. Each chronology must refer to an enum or similar singleton to provide the era values. This method returns the singleton era of the correct type for the specified era value.
`MutableList<Era!>!`	`eras()` Gets the list of eras for the chronology. Most calendar systems have an era, within which the year has meaning. If the calendar system does not support the concept of eras, an empty list must be returned.
`String!`	`getCalendarType()` Gets the calendar type of the calendar system. The calendar type is an identifier defined by the CLDR and Unicode Locale Data Markup Language (LDML) specifications to uniquely identify a calendar. The `getCalendarType` is the concatenation of the CLDR calendar type and the variant, if applicable, is appended separated by "-". The calendar type is used to lookup the `Chronology` using `of(java.lang.String)`.
`String!`	`getDisplayName(style: TextStyle!, locale: Locale!)` Gets the textual representation of this chronology. This returns the textual name used to identify the chronology, suitable for presentation to the user. The parameters control the style of the returned text and the locale.
`String!`	`getId()` Gets the ID of the chronology. The ID uniquely identifies the `Chronology`. It can be used to lookup the `Chronology` using `of(java.lang.String)`.
`Boolean`	`isLeapYear(prolepticYear: Long)` Checks if the specified year is a leap year. A leap-year is a year of a longer length than normal. The exact meaning is determined by the chronology according to the following constraints. a leap-year must imply a year-length longer than a non leap-year. a chronology that does not support the concept of a year must return false. the correct result must be returned for all years within the valid range of years for the chronology. Outside the range of valid years an implementation is free to return either a best guess or false. An implementation must not throw an exception, even if the year is outside the range of valid years.
`ChronoLocalDateTime<out ChronoLocalDate!>!`	`localDateTime(temporal: TemporalAccessor!)` Obtains a local date-time in this chronology from another temporal object. This obtains a date-time in this chronology based on the specified temporal. A `TemporalAccessor` represents an arbitrary set of date and time information, which this factory converts to an instance of `ChronoLocalDateTime`. The conversion extracts and combines the `ChronoLocalDate` and the `LocalTime` from the temporal object. Implementations are permitted to perform optimizations such as accessing those fields that are equivalent to the relevant objects. The result uses this chronology. This method matches the signature of the functional interface `TemporalQuery` allowing it to be used as a query via method reference, `aChronology::localDateTime`.
`ChronoPeriod!`	`period(years: Int, months: Int, days: Int)` Obtains a period for this chronology based on years, months and days. This returns a period tied to this chronology using the specified years, months and days. All supplied chronologies use periods based on years, months and days, however the `ChronoPeriod` API allows the period to be represented using other units.
`Int`	`prolepticYear(era: Era!, yearOfEra: Int)` Calculates the proleptic-year given the era and year-of-era. This combines the era and year-of-era into the single proleptic-year field. If the chronology makes active use of eras, such as `JapaneseChronology` then the year-of-era will be validated against the era. For other chronologies, validation is optional.
`ValueRange!`	`range(field: ChronoField!)` Gets the range of valid values for the specified field. All fields can be expressed as a `long` integer. This method returns an object that describes the valid range for that value. 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. This method will return a result whether or not the chronology supports the field.
`ChronoZonedDateTime<out ChronoLocalDate!>!`	`zonedDateTime(instant: Instant!, zone: ZoneId!)` Obtains a `ChronoZonedDateTime` in this chronology from an `Instant`. This obtains a zoned date-time with the same instant as that specified.
`ChronoZonedDateTime<out ChronoLocalDate!>!`	`zonedDateTime(temporal: TemporalAccessor!)` Obtains a `ChronoZonedDateTime` in this chronology from another temporal object. This obtains a zoned date-time in this chronology based on the specified temporal. A `TemporalAccessor` represents an arbitrary set of date and time information, which this factory converts to an instance of `ChronoZonedDateTime`. The conversion will first obtain a `ZoneId` from the temporal object, falling back to a `ZoneOffset` if necessary. It will then try to obtain an `Instant`, falling back to a `ChronoLocalDateTime` if necessary. The result will be either the combination of `ZoneId` or `ZoneOffset` with `Instant` or `ChronoLocalDateTime`. Implementations are permitted to perform optimizations such as accessing those fields that are equivalent to the relevant objects. The result uses this chronology. This method matches the signature of the functional interface `TemporalQuery` allowing it to be used as a query via method reference, `aChronology::zonedDateTime`.

Properties
static ThaiBuddhistChronology!	`INSTANCE` Singleton instance of the Buddhist chronology.

Public methods

date

Added in API level 26

fun date(
    prolepticYear: Int, 
    month: Int, 
    dayOfMonth: Int
): ThaiBuddhistDate!

Obtains a local date in Thai Buddhist calendar system from the proleptic-year, month-of-year and day-of-month fields.

Parameters
`prolepticYear`	Int: the proleptic-year
`month`	Int: the month-of-year
`dayOfMonth`	Int: the day-of-month

Return
`ThaiBuddhistDate!`	the Thai Buddhist local date, not null

Exceptions
`java.time.DateTimeException`	if unable to create the date

date

Added in API level 26

fun date(
    era: Era!, 
    yearOfEra: Int, 
    month: Int, 
    dayOfMonth: Int
): ThaiBuddhistDate!

Obtains a local date in Thai Buddhist calendar system from the era, year-of-era, month-of-year and day-of-month fields.

Parameters
`era`	Era!: the Thai Buddhist era, not null
`yearOfEra`	Int: the year-of-era
`month`	Int: the month-of-year
`dayOfMonth`	Int: the day-of-month

Return
`ThaiBuddhistDate!`	the Thai Buddhist local date, not null

Exceptions
`java.lang.ClassCastException`	if the `era` is not a `ThaiBuddhistEra`
`java.time.DateTimeException`	if unable to create the date

date

Added in API level 26

fun date(temporal: TemporalAccessor!): ThaiBuddhistDate!

Obtains a local date in this chronology from another temporal object.

This obtains a date in this chronology based on the specified temporal. A TemporalAccessor represents an arbitrary set of date and time information, which this factory converts to an instance of ChronoLocalDate.

The conversion typically uses the EPOCH_DAY field, which is standardized across calendar systems.

This method matches the signature of the functional interface TemporalQuery allowing it to be used as a query via method reference, aChronology::date.

Parameters
`temporal`	TemporalAccessor!: the temporal object to convert, not null

Return
`ThaiBuddhistDate!`	the local date in this chronology, not null

Exceptions
`java.time.DateTimeException`	if unable to create the date

dateEpochDay

Added in API level 26

fun dateEpochDay(epochDay: Long): ThaiBuddhistDate!

Obtains a local date in the Thai Buddhist calendar system from the epoch-day.

Parameters
`epochDay`	Long: the epoch day

Return
`ThaiBuddhistDate!`	the Thai Buddhist local date, not null

Exceptions
`java.time.DateTimeException`	if unable to create the date

dateNow

Added in API level 26

fun dateNow(): ThaiBuddhistDate!

Obtains the current local date in this chronology from the system clock in the default time-zone.

This will query the system clock in the default time-zone to obtain the current date.

Using this method will prevent the ability to use an alternate clock for testing because the clock is hard-coded.

Return
`ThaiBuddhistDate!`	the current local date using the system clock and default time-zone, not null

Exceptions
`java.time.DateTimeException`	if unable to create the date

dateNow

Added in API level 26

fun dateNow(clock: Clock!): ThaiBuddhistDate!

Obtains the current local date in this chronology from the specified clock.

This will query the specified clock to obtain the current date - today. Using this method allows the use of an alternate clock for testing. The alternate clock may be introduced using dependency injection.

Parameters
`clock`	Clock!: the clock to use, not null

Return
`ThaiBuddhistDate!`	the current local date, not null

Exceptions
`java.time.DateTimeException`	if unable to create the date

dateNow

Added in API level 26

fun dateNow(zone: ZoneId!): ThaiBuddhistDate!

Obtains the current local date in this chronology from the system clock in the specified time-zone.

This will query the system clock to obtain the current date. Specifying the time-zone avoids dependence on the default time-zone.

Using this method will prevent the ability to use an alternate clock for testing because the clock is hard-coded.

Parameters
`zone`	ZoneId!: the zone ID to use, not null

Return
`ThaiBuddhistDate!`	the current local date using the system clock, not null

Exceptions
`java.time.DateTimeException`	if unable to create the date

dateYearDay

Added in API level 26

fun dateYearDay(
    prolepticYear: Int, 
    dayOfYear: Int
): ThaiBuddhistDate!

Obtains a local date in Thai Buddhist calendar system from the proleptic-year and day-of-year fields.

Parameters
`prolepticYear`	Int: the proleptic-year
`dayOfYear`	Int: the day-of-year

Return
`ThaiBuddhistDate!`	the Thai Buddhist local date, not null

Exceptions
`java.time.DateTimeException`	if unable to create the date

dateYearDay

Added in API level 26

fun dateYearDay(
    era: Era!, 
    yearOfEra: Int, 
    dayOfYear: Int
): ThaiBuddhistDate!

Obtains a local date in Thai Buddhist calendar system from the era, year-of-era and day-of-year fields.

Parameters
`era`	Era!: the Thai Buddhist era, not null
`yearOfEra`	Int: the year-of-era
`dayOfYear`	Int: the day-of-year

Return
`ThaiBuddhistDate!`	the Thai Buddhist local date, not null

Exceptions
`java.lang.ClassCastException`	if the `era` is not a `ThaiBuddhistEra`
`java.time.DateTimeException`	if unable to create the date

eraOf

Added in API level 26

fun eraOf(eraValue: Int): ThaiBuddhistEra!

Creates the chronology era object from the numeric value.

The era is, conceptually, the largest division of the time-line. Most calendar systems have a single epoch dividing the time-line into two eras. However, some have multiple eras, such as one for the reign of each leader. The exact meaning is determined by the chronology according to the following constraints.

The era in use at 1970-01-01 must have the value 1. Later eras must have sequentially higher values. Earlier eras must have sequentially lower values. Each chronology must refer to an enum or similar singleton to provide the era values.

This method returns the singleton era of the correct type for the specified era value.

Parameters
`eraValue`	Int: the era value

Return
`ThaiBuddhistEra!`	the calendar system era, not null

Exceptions
`java.time.DateTimeException`	if unable to create the era

eras

Added in API level 26

fun eras(): MutableList<Era!>!

Gets the list of eras for the chronology.

Most calendar systems have an era, within which the year has meaning. If the calendar system does not support the concept of eras, an empty list must be returned.

Return
`MutableList<Era!>!`	the list of eras for the chronology, may be immutable, not null

getCalendarType

Added in API level 26

fun getCalendarType(): String!

Gets the calendar type of the underlying calendar system - 'buddhist'.

The calendar type is an identifier defined by the Unicode Locale Data Markup Language (LDML) specification. It can be used to lookup the Chronology using Chronology.of(String). It can also be used as part of a locale, accessible via Locale.getUnicodeLocaleType(String) with the key 'ca'.

Return
`String!`	the calendar system type - 'buddhist'

See Also

#getId()

getId

Added in API level 26

fun getId(): String!

Gets the ID of the chronology - 'ThaiBuddhist'.

The ID uniquely identifies the Chronology. It can be used to lookup the Chronology using Chronology.of(String).

Return
`String!`	the chronology ID - 'ThaiBuddhist'

See Also

#getCalendarType()

isLeapYear

Added in API level 26

fun isLeapYear(prolepticYear: Long): Boolean

Checks if the specified year is a leap year.

Thai Buddhist leap years occur exactly in line with ISO leap years. This method does not validate the year passed in, and only has a well-defined result for years in the supported range.

Parameters
`prolepticYear`	Long: the proleptic-year to check, not validated for range

Return
`Boolean`	true if the year is a leap year

localDateTime

Added in API level 26

fun localDateTime(temporal: TemporalAccessor!): ChronoLocalDateTime<ThaiBuddhistDate!>!

Obtains a local date-time in this chronology from another temporal object.

This obtains a date-time in this chronology based on the specified temporal. A TemporalAccessor represents an arbitrary set of date and time information, which this factory converts to an instance of ChronoLocalDateTime.

The conversion extracts and combines the ChronoLocalDate and the LocalTime from the temporal object. Implementations are permitted to perform optimizations such as accessing those fields that are equivalent to the relevant objects. The result uses this chronology.

This method matches the signature of the functional interface TemporalQuery allowing it to be used as a query via method reference, aChronology::localDateTime.

Parameters
`temporal`	TemporalAccessor!: the temporal object to convert, not null

Return
`ChronoLocalDateTime<ThaiBuddhistDate!>!`	the local date-time in this chronology, not null

Exceptions
`java.time.DateTimeException`	if unable to create the date-time

prolepticYear

Added in API level 26

fun prolepticYear(
    era: Era!, 
    yearOfEra: Int
): Int

Calculates the proleptic-year given the era and year-of-era.

This combines the era and year-of-era into the single proleptic-year field.

If the chronology makes active use of eras, such as JapaneseChronology then the year-of-era will be validated against the era. For other chronologies, validation is optional.

Parameters
`era`	Era!: the era of the correct type for the chronology, not null
`yearOfEra`	Int: the chronology year-of-era

Return
`Int`	the proleptic-year

Exceptions
`java.lang.ClassCastException`	if the `era` is not of the correct type for the chronology
`java.time.DateTimeException`	if unable to convert to a proleptic-year, such as if the year is invalid for the era

range

Added in API level 26

fun range(field: ChronoField!): ValueRange!

Gets the range of valid values for the specified field.

All fields can be expressed as a long integer. This method returns an object that describes the valid range for that value.

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.

This method will return a result whether or not the chronology supports the field.

Parameters
`field`	ChronoField!: the field to get the range for, not null

Return
`ValueRange!`	the range of valid values for the field, not null

Exceptions
`java.time.DateTimeException`	if the range for the field cannot be obtained

resolveDate

Added in API level 26

fun resolveDate(
    fieldValues: MutableMap<TemporalField!, Long!>!, 
    resolverStyle: ResolverStyle!
): ThaiBuddhistDate!

Resolves parsed ChronoField values into a date during parsing.

Most TemporalField implementations are resolved using the resolve method on the field. By contrast, the ChronoField class defines fields that only have meaning relative to the chronology. As such, ChronoField date fields are resolved here in the context of a specific chronology.

ChronoField instances are resolved by this method, which may be overridden in subclasses.

EPOCH_DAY - If present, this is converted to a date and all other date fields are then cross-checked against the date.
PROLEPTIC_MONTH - If present, then it is split into the YEAR and MONTH_OF_YEAR. If the mode is strict or smart then the field is validated.
YEAR_OF_ERA and ERA - If both are present, then they are combined to form a YEAR. In lenient mode, the YEAR_OF_ERA range is not validated, in smart and strict mode it is. The ERA is validated for range in all three modes. If only the YEAR_OF_ERA is present, and the mode is smart or lenient, then the last available era is assumed. In strict mode, no era is assumed and the YEAR_OF_ERA is left untouched. If only the ERA is present, then it is left untouched.
YEAR, MONTH_OF_YEAR and DAY_OF_MONTH - If all three are present, then they are combined to form a date. In all three modes, the YEAR is validated. If the mode is smart or strict, then the month and day are validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first day of the first month in the requested year, then adding the difference in months, then the difference in days. If the mode is smart, and the day-of-month is greater than the maximum for the year-month, then the day-of-month is adjusted to the last day-of-month. If the mode is strict, then the three fields must form a valid date.
YEAR and DAY_OF_YEAR - If both are present, then they are combined to form a date. In all three modes, the YEAR is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first day of the requested year, then adding the difference in days. If the mode is smart or strict, then the two fields must form a valid date.
YEAR, MONTH_OF_YEAR, ALIGNED_WEEK_OF_MONTH and ALIGNED_DAY_OF_WEEK_IN_MONTH - If all four are present, then they are combined to form a date. In all three modes, the YEAR is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first day of the first month in the requested year, then adding the difference in months, then the difference in weeks, then in days. If the mode is smart or strict, then the all four fields are validated to their outer ranges. The date is then combined in a manner equivalent to creating a date on the first day of the requested year and month, then adding the amount in weeks and days to reach their values. If the mode is strict, the date is additionally validated to check that the day and week adjustment did not change the month.
YEAR, MONTH_OF_YEAR, ALIGNED_WEEK_OF_MONTH and DAY_OF_WEEK - If all four are present, then they are combined to form a date. The approach is the same as described above for years, months and weeks in ALIGNED_DAY_OF_WEEK_IN_MONTH. The day-of-week is adjusted as the next or same matching day-of-week once the years, months and weeks have been handled.
YEAR, ALIGNED_WEEK_OF_YEAR and ALIGNED_DAY_OF_WEEK_IN_YEAR - If all three are present, then they are combined to form a date. In all three modes, the YEAR is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first day of the requested year, then adding the difference in weeks, then in days. If the mode is smart or strict, then the all three fields are validated to their outer ranges. The date is then combined in a manner equivalent to creating a date on the first day of the requested year, then adding the amount in weeks and days to reach their values. If the mode is strict, the date is additionally validated to check that the day and week adjustment did not change the year.
YEAR, ALIGNED_WEEK_OF_YEAR and DAY_OF_WEEK - If all three are present, then they are combined to form a date. The approach is the same as described above for years and weeks in ALIGNED_DAY_OF_WEEK_IN_YEAR. The day-of-week is adjusted as the next or same matching day-of-week once the years and weeks have been handled.

The default implementation is suitable for most calendar systems. If java.time.temporal.ChronoField#YEAR_OF_ERA is found without an java.time.temporal.ChronoField#ERA then the last era in eras() is used. The implementation assumes a 7 day week, that the first day-of-month has the value 1, that first day-of-year has the value 1, and that the first of the month and year always exists.

Parameters
`fieldValues`	MutableMap<TemporalField!, Long!>!: the map of fields to values, which can be updated, not null
`resolverStyle`	ResolverStyle!: the requested type of resolve, not null

Return
`ThaiBuddhistDate!`	the resolved date, null if insufficient information to create a date

Exceptions
`java.time.DateTimeException`	if the date cannot be resolved, typically because of a conflict in the input data

zonedDateTime

Added in API level 26

fun zonedDateTime(
    instant: Instant!, 
    zone: ZoneId!
): ChronoZonedDateTime<ThaiBuddhistDate!>!

Obtains a ChronoZonedDateTime in this chronology from an Instant.

This obtains a zoned date-time with the same instant as that specified.

Parameters
`instant`	Instant!: the instant to create the date-time from, not null
`zone`	ZoneId!: the time-zone, not null

Return
`ChronoZonedDateTime<ThaiBuddhistDate!>!`	the zoned date-time, not null

Exceptions
`java.time.DateTimeException`	if the result exceeds the supported range

zonedDateTime

Added in API level 26

fun zonedDateTime(temporal: TemporalAccessor!): ChronoZonedDateTime<ThaiBuddhistDate!>!

Obtains a ChronoZonedDateTime in this chronology from another temporal object.

This obtains a zoned date-time in this chronology based on the specified temporal. A TemporalAccessor represents an arbitrary set of date and time information, which this factory converts to an instance of ChronoZonedDateTime.

The conversion will first obtain a ZoneId from the temporal object, falling back to a ZoneOffset if necessary. It will then try to obtain an Instant, falling back to a ChronoLocalDateTime if necessary. The result will be either the combination of ZoneId or ZoneOffset with Instant or ChronoLocalDateTime. Implementations are permitted to perform optimizations such as accessing those fields that are equivalent to the relevant objects. The result uses this chronology.

This method matches the signature of the functional interface TemporalQuery allowing it to be used as a query via method reference, aChronology::zonedDateTime.

Parameters
`temporal`	TemporalAccessor!: the temporal object to convert, not null

Return
`ChronoZonedDateTime<ThaiBuddhistDate!>!`	the zoned date-time in this chronology, not null

Exceptions
`java.time.DateTimeException`	if unable to create the date-time

Properties

INSTANCE

Added in API level 26

static val INSTANCE: ThaiBuddhistChronology!

Singleton instance of the Buddhist chronology.