-
-
Notifications
You must be signed in to change notification settings - Fork 36
Require select option to be set by a literal value #1016
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
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
aphillips
approved these changes
Feb 17, 2025
sffc
reviewed
Feb 17, 2025
"exp": "literal select {1}" | ||
}, | ||
{ | ||
"src": ".local $bad = {exact} {{variable select {1 :number select=$bad}}}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: add a test similar to this one but with .input
catamorphism
added a commit
to catamorphism/icu
that referenced
this pull request
Mar 1, 2025
Update spec tests to current version from message-format-wg - Update parser for changed name-start grammar rule - Validate number literals in :number implementation (since parser no longer does this) - Disallow `:number`/`:integer` select option set from variable See unicode-org/message-format-wg#1016 As part of this, un-skip tests where the `bad-option` error is expected, and implement validating digit size options (pending PR unicode-org#2973 is intended to do this more fully)
6 tasks
catamorphism
added a commit
to catamorphism/icu
that referenced
this pull request
Mar 1, 2025
Update spec tests to current version from message-format-wg - Update parser for changed name-start grammar rule - Validate number literals in :number implementation (since parser no longer does this) - Disallow `:number`/`:integer` select option set from variable See unicode-org/message-format-wg#1016 As part of this, un-skip tests where the `bad-option` error is expected, and implement validating digit size options (pending PR unicode-org#2973 is intended to do this more fully)
eemeli
added a commit
to messageformat/messageformat
that referenced
this pull request
Mar 2, 2025
catamorphism
added a commit
to catamorphism/icu
that referenced
this pull request
Mar 3, 2025
Update spec tests to current version from message-format-wg - Update parser for changed name-start grammar rule - Validate number literals in :number implementation (since parser no longer does this) - Disallow `:number`/`:integer` select option set from variable See unicode-org/message-format-wg#1016 As part of this, un-skip tests where the `bad-option` error is expected, and implement validating digit size options (pending PR unicode-org#2973 is intended to do this more fully)
catamorphism
added a commit
to catamorphism/icu
that referenced
this pull request
Mar 13, 2025
Update spec tests to current version from message-format-wg - Update parser for changed name-start grammar rule - Validate number literals in :number implementation (since parser no longer does this) - Disallow `:number`/`:integer` select option set from variable See unicode-org/message-format-wg#1016 As part of this, un-skip tests where the `bad-option` error is expected, and implement validating digit size options (pending PR unicode-org#2973 is intended to do this more fully)
catamorphism
added a commit
to catamorphism/icu
that referenced
this pull request
Mar 27, 2025
Update spec tests to current version from message-format-wg - Update parser for changed name-start grammar rule - Validate number literals in :number implementation (since parser no longer does this) - Disallow `:number`/`:integer` select option set from variable See unicode-org/message-format-wg#1016 As part of this, un-skip tests where the `bad-option` error is expected, and implement validating digit size options (pending PR unicode-org#2973 is intended to do this more fully)
catamorphism
added a commit
to unicode-org/icu
that referenced
this pull request
Mar 27, 2025
Update spec tests to current version from message-format-wg - Update parser for changed name-start grammar rule - Validate number literals in :number implementation (since parser no longer does this) - Disallow `:number`/`:integer` select option set from variable See unicode-org/message-format-wg#1016 As part of this, un-skip tests where the `bad-option` error is expected, and implement validating digit size options (pending PR #2973 is intended to do this more fully)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For context, see #1006
As pointed out by @aphillips in a comment on the ICU4X-TC feedback doc:
We can't really make using a variable for
select
a syntax or data model error unless we add a really special case for it in the Syntax part, but this is nearly that.Note that as shown in the test cases, formatting the following message would result in
bad-option
andbad-selector
errors: