Conversation
…verting to options
…ures, simplify DateToken, export getDateTimeFormatOptions()
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces breaking changes to
@messageformat/date-skeletonand@messageformat/number-skeleton, as the required language capabilities are updated, and the publicDateTokeninterface is changed.The tools are updated to make use of Intl.DateTimeFormat and Intl.NumberFormat features up to ES2023, so more patterns and skeletons can be represented. This also moves some of the validation from parsing to options bag construction.
All number format skeleton features documented here are now supported, including concise-syntax tokens.
The previously internal functions
getDateTimeFormatOptions()andgetNumberFormatOptions()are now exported, for use in particular by@messageformat/icu-messageformat-1.