Stay organized with collections
Save and categorize content based on your preferences.
ResolverStyle
class ResolverStyle
Enumeration of different ways to resolve dates and times.
Parsing a text string occurs in two phases. Phase 1 is a basic text parse according to the fields added to the builder. Phase 2 resolves the parsed field-value pairs into date and/or time objects. This style is used to control how phase 2, resolving, happens.
Summary
Enum values |
Style to resolve dates and times leniently.
|
Style to resolve dates and times in a smart, or intelligent, manner.
|
Style to resolve dates and times strictly.
|
Enum values
LENIENT
enum val LENIENT : ResolverStyle
Style to resolve dates and times leniently.
Using lenient resolution will resolve the values in an appropriate lenient manner. Individual fields will interpret this differently.
For example, lenient mode allows the month in the ISO calendar system to be outside the range 1 to 12. For example, month 15 is treated as being 3 months after month 12.
SMART
enum val SMART : ResolverStyle
Style to resolve dates and times in a smart, or intelligent, manner.
Using smart resolution will perform the sensible default for each field, which may be the same as strict, the same as lenient, or a third behavior. Individual fields will interpret this differently.
For example, resolving year-month and day-of-month in the ISO calendar system using smart mode will ensure that the day-of-month is from 1 to 31, converting any value beyond the last valid day-of-month to be the last valid day-of-month.
STRICT
enum val STRICT : ResolverStyle
Style to resolve dates and times strictly.
Using strict resolution will ensure that all parsed values are within the outer range of valid values for the field. Individual fields may be further processed for strictness.
For example, resolving year-month and day-of-month in the ISO calendar system using strict mode will ensure that the day-of-month is valid for the year-month, rejecting invalid values.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-02-10 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-10 UTC."],[],[],null,["# ResolverStyle\n\nAdded in [API level 26](https://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)\n\nResolverStyle\n=============\n\n```\nclass ResolverStyle\n```\n\n|---|---|-------------------------------------|\n| [kotlin.Any](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-any/index.html) |||\n| ↳ | [kotlin.Enum](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-enum/index.html)\\\u003c[java.time.format.ResolverStyle](#)\\\u003e ||\n| | ↳ | [java.time.format.ResolverStyle](#) |\n\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Known Direct Subclasses [ResolverStyle.LENIENT](#ENUM_VALUE:LENIENT), [ResolverStyle.SMART](#ENUM_VALUE:SMART), [ResolverStyle.STRICT](#ENUM_VALUE:STRICT) |----------------------------------------------|----------------------------------------------------------------------| | [ResolverStyle.LENIENT](#ENUM_VALUE:LENIENT) | Style to resolve dates and times leniently. | | [ResolverStyle.SMART](#ENUM_VALUE:SMART) | Style to resolve dates and times in a smart, or intelligent, manner. | | [ResolverStyle.STRICT](#ENUM_VALUE:STRICT) | Style to resolve dates and times strictly. | |\n\nEnumeration of different ways to resolve dates and times.\n\nParsing a text string occurs in two phases. Phase 1 is a basic text parse according to the fields added to the builder. Phase 2 resolves the parsed field-value pairs into date and/or time objects. This style is used to control how phase 2, resolving, happens.\n\nSummary\n-------\n\n| Enum values ||\n|-------------------------------------------------------------------------------------------------|---|\n| [LENIENT](#ENUM_VALUE:LENIENT) Style to resolve dates and times leniently. |\n| [SMART](#ENUM_VALUE:SMART) Style to resolve dates and times in a smart, or intelligent, manner. |\n| [STRICT](#ENUM_VALUE:STRICT) Style to resolve dates and times strictly. |\n\nEnum values\n-----------\n\n### LENIENT\n\nAdded in [API level 26](https://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels) \n\n```\nenum val LENIENT : ResolverStyle\n```\n\nStyle to resolve dates and times leniently.\n\nUsing lenient resolution will resolve the values in an appropriate lenient manner. Individual fields will interpret this differently.\n\nFor example, lenient mode allows the month in the ISO calendar system to be outside the range 1 to 12. For example, month 15 is treated as being 3 months after month 12. \n\n### SMART\n\nAdded in [API level 26](https://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels) \n\n```\nenum val SMART : ResolverStyle\n```\n\nStyle to resolve dates and times in a smart, or intelligent, manner.\n\nUsing smart resolution will perform the sensible default for each field, which may be the same as strict, the same as lenient, or a third behavior. Individual fields will interpret this differently.\n\nFor example, resolving year-month and day-of-month in the ISO calendar system using smart mode will ensure that the day-of-month is from 1 to 31, converting any value beyond the last valid day-of-month to be the last valid day-of-month. \n\n### STRICT\n\nAdded in [API level 26](https://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels) \n\n```\nenum val STRICT : ResolverStyle\n```\n\nStyle to resolve dates and times strictly.\n\nUsing strict resolution will ensure that all parsed values are within the outer range of valid values for the field. Individual fields may be further processed for strictness.\n\nFor example, resolving year-month and day-of-month in the ISO calendar system using strict mode will ensure that the day-of-month is valid for the year-month, rejecting invalid values."]]