Returns a field to access the day of week based on this WeekFields
.
Returns a field to access the day of week based on this WeekFields
.
This is similar to ChronoField#DAY_OF_WEEK
but uses values for the day-of-week based on
this WeekFields
. The days are numbered from 1 to 7 where the #getFirstDayOfWeek() first day-of-week
is assigned the value 1.
For example, if the first day-of-week is Sunday, then that will have the value 1, with other days ranging from Monday as 2 to Saturday as 7.
In the resolving phase of parsing, a localized day-of-week will be converted to a standardized
ChronoField
day-of-week. The day-of-week must be in the valid range 1 to 7. Other
fields in this class build dates using the standardized day-of-week.
a field providing access to the day-of-week with localized numbering, not null
Checks if this WeekFields
is equal to the specified object.
Checks if this WeekFields
is equal to the specified object.
The comparison is based on the entire state of the rules, which is the first day-of-week and minimal days.
the other rules to compare to, null returns false
true if this is equal to the specified rules
Gets the first day-of-week.
Gets the first day-of-week.
The first day-of-week varies by culture. For example, the US uses Sunday, while France and the
ISO-8601 standard use Monday. This method returns the first day using the standard
DayOfWeek
enum.
the first day-of-week, not null
Gets the minimal number of days in the first week.
Gets the minimal number of days in the first week.
The number of days considered to define the first week of a month or year varies by culture. For example, the ISO-8601 requires 4 days (more than half a week) to be present before counting the first week.
the minimal number of days in the first week of a month or year, from 1 to 7
A hash code for this WeekFields
.
A hash code for this WeekFields
.
a suitable hash code
A string representation of this WeekFields
instance.
A string representation of this WeekFields
instance.
the string representation, not null
Returns a field to access the year of a week-based-year based on this WeekFields
.
Returns a field to access the year of a week-based-year based on this WeekFields
.
This represents the concept of the year where weeks start on a fixed day-of-week, such as
Monday and each week belongs to exactly one year. This field is typically used with WeekFields#dayOfWeek()
and WeekFields#weekOfWeekBasedYear()
.
Week one(1) is the week starting on the WeekFields#getFirstDayOfWeek
where there are at
least WeekFields#getMinimalDaysInFirstWeek()
days in the year. Thus, week one may start
before the start of the year. If the first week starts after the start of the year then the
period before is in the last week of the previous year.
This field can be used with any calendar system.
In the resolving phase of parsing, a date can be created from a week-based-year, week-of-year and day-of-week.
In strict mode, all three fields are validated against their range of valid values. The week-of-year field is validated to ensure that the resulting week-based-year is the week-based-year requested.
In smart mode, all three fields are validated against their range of valid values. The week-of-week-based-year field is validated from 1 to 53, meaning that the resulting date can be in the following week-based-year to that specified.
In lenient mode, the year and day-of-week are validated against the range of valid values. The resulting date is calculated equivalent to the following three stage approach. First, create a date on the first day of the first week in the requested week-based-year. Then take the week-of-week-based-year, subtract one, and add the amount in weeks to the date. Finally, adjust to the correct day-of-week within the localized week.
a field providing access to the week-based-year, not null
Returns a field to access the week of month based on this WeekFields
.
Returns a field to access the week of month based on this WeekFields
.
This represents the concept of the count of weeks within the month where weeks start on a fixed
day-of-week, such as Monday. This field is typically used with WeekFields#dayOfWeek()
.
Week one (1) is the week starting on the WeekFields#getFirstDayOfWeek
where there are
at least WeekFields#getMinimalDaysInFirstWeek()
days in the month. Thus, week one may
start up to minDays
days before the start of the month. If the first week starts after
the start of the month then the period before is week zero (0).
For example:
This field can be used with any calendar system.
In the resolving phase of parsing, a date can be created from a year, week-of-month, month-of-year and day-of-week.
In strict mode, all four fields are validated against their range of valid values. The week-of-month field is validated to ensure that the resulting month is the month requested.
In smart mode, all four fields are validated against their range of valid values. The week-of-month field is validated from 0 to 6, meaning that the resulting date can be in a different month to that specified.
In lenient mode, the year and day-of-week are validated against the range of valid values. The resulting date is calculated equivalent to the following four stage approach. First, create a date on the first day of the first week of January in the requested year. Then take the month-of-year, subtract one, and add the amount in months to the date. Then take the week-of-month, subtract one, and add the amount in weeks to the date. Finally, adjust to the correct day-of-week within the localized week.
a field providing access to the week-of-month, not null
Returns a field to access the week of a week-based-year based on this WeekFields
.
Returns a field to access the week of a week-based-year based on this WeekFields
.
This represents the concept of the count of weeks within the year where weeks start on a fixed
day-of-week, such as Monday and each week belongs to exactly one year. This field is typically
used with WeekFields#dayOfWeek()
and WeekFields#weekBasedYear()
.
Week one(1) is the week starting on the WeekFields#getFirstDayOfWeek
where there are at
least WeekFields#getMinimalDaysInFirstWeek()
days in the year. If the first week starts
after the start of the year then the period before is in the last week of the previous year.
For example:
This field can be used with any calendar system.
In the resolving phase of parsing, a date can be created from a week-based-year, week-of-year and day-of-week.
In strict mode, all three fields are validated against their range of valid values. The week-of-year field is validated to ensure that the resulting week-based-year is the week-based-year requested.
In smart mode, all three fields are validated against their range of valid values. The week-of-week-based-year field is validated from 1 to 53, meaning that the resulting date can be in the following week-based-year to that specified.
In lenient mode, the year and day-of-week are validated against the range of valid values. The resulting date is calculated equivalent to the following three stage approach. First, create a date on the first day of the first week in the requested week-based-year. Then take the week-of-week-based-year, subtract one, and add the amount in weeks to the date. Finally, adjust to the correct day-of-week within the localized week.
a field providing access to the week-of-week-based-year, not null
Returns a field to access the week of year based on this WeekFields
.
Returns a field to access the week of year based on this WeekFields
.
This represents the concept of the count of weeks within the year where weeks start on a fixed
day-of-week, such as Monday. This field is typically used with WeekFields#dayOfWeek()
.
Week one(1) is the week starting on the WeekFields#getFirstDayOfWeek
where there are at
least WeekFields#getMinimalDaysInFirstWeek()
days in the year. Thus, week one may start
up to minDays
days before the start of the year. If the first week starts after the
start of the year then the period before is week zero (0).
For example:
This field can be used with any calendar system.
In the resolving phase of parsing, a date can be created from a year, week-of-year and day-of-week.
In strict mode, all three fields are validated against their range of valid values. The week-of-year field is validated to ensure that the resulting year is the year requested.
In smart mode, all three fields are validated against their range of valid values. The week-of-year field is validated from 0 to 54, meaning that the resulting date can be in a different year to that specified.
In lenient mode, the year and day-of-week are validated against the range of valid values. The resulting date is calculated equivalent to the following three stage approach. First, create a date on the first day of the first week in the requested year. Then take the week-of-year, subtract one, and add the amount in weeks to the date. Finally, adjust to the correct day-of-week within the localized week.
a field providing access to the week-of-year, not null
Localized definitions of the day-of-week, week-of-month and week-of-year fields.
A standard week is seven days long, but cultures have different definitions for some other aspects of a week. This class represents the definition of the week, for the purpose of providing
TemporalField
instances.WeekFields provides three fields,
#dayOfWeek()
,#weekOfMonth()
, and#weekOfYear()
that provide access to the values from anytemporal object
.The computations for day-of-week, week-of-month, and week-of-year are based on the
ChronoField#YEAR proleptic-year
,month-of-year
,ChronoField#DAY_OF_MONTH day-of-month
, andISO day-of-week
which are based on theepoch-day
and the chronology. The values may not be aligned with theyear-of-Era
depending on the Chronology. A week is defined by:Together these two values allow a year or month to be divided into weeks.
Week of Month
One field is used: week-of-month. The calculation ensures that weeks never overlap a month boundary. The month is divided into periods where each period starts on the defined first day-of-week. The earliest period is referred to as week 0 if it has less than the minimal number of days and week 1 if it has at least the minimal number of days.
Minimal days: 4
Minimal days: 5
IllegalArgumentException
if the minimal days value is invalid