Skip to content
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

ICU-23059 Update spec tests #3415

Merged

Conversation

catamorphism
Copy link
Contributor

@catamorphism catamorphism commented Feb 25, 2025

This updates the MF2 spec tests to unicode-org/message-format-wg@943479b with the following exceptions:

  • functions/currency.json and functions/math.json are omitted because these are not yet implemented

  • bidi.json will be handled in a future PR

  • u-options.json will be handled in a future PR

Changes include:
* :integer now returns a value encapsulating the rounded numeric value of the argument, rather than
the value itself.
* Fallbacks are handled according to the current spec.
* Fallback values are not passed into functions.
* Characters inside literal fallbacks are properly escaped.
* The test runner skips null values properly.
* The test runner handles boolean expErrors in defaultTestProperties.
* :string normalizes its input and normalizeNFC() has been refactored so it can be called there.

Checklist

  • Required: Issue filed: ICU-23059
  • Required: The PR title must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
  • Required: Each commit message must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
  • Issue accepted (done by Technical Committee after discussion)
  • Tests included, if applicable
  • API docs and/or User Guide docs changed or added, if applicable

@catamorphism catamorphism force-pushed the february-2025-spec-tests branch from 3879983 to 20e8d2a Compare February 25, 2025 03:31
@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • icu4c/source/i18n/messageformat2_evaluation.cpp is different
  • icu4c/source/i18n/messageformat2_function_registry.cpp is different
  • icu4c/source/i18n/messageformat2.cpp is different
  • icu4c/source/i18n/unicode/messageformat2.h is different
  • icu4c/source/test/intltest/messageformat2test_read_json.cpp is different
  • icu4c/source/test/intltest/messageformat2test_utils.h is now changed in the branch
  • testdata/message2/more-functions.json is now changed in the branch
  • testdata/message2/spec/fallback.json is now changed in the branch

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

This updates the MF2 spec tests to unicode-org/message-format-wg@943479b with the following exceptions:

- functions/currency.json and functions/math.json are omitted because these are not yet implemented

- bidi.json will be handled in a future PR

- u-options.json will be handled in a future PR

Changes include:
* `:integer` now returns a value encapsulating the rounded numeric value of the argument, rather than
  the value itself.
* Fallbacks are handled according to the current spec.
* Fallback values are not passed into functions.
* Characters inside literal fallbacks are properly escaped.
* The test runner skips null values properly.
* The test runner handles boolean `expErrors` in defaultTestProperties.
* `:string` normalizes its input and normalizeNFC() has been refactored so it can be called there.
@catamorphism catamorphism force-pushed the february-2025-spec-tests branch from 6112d3e to c546c6b Compare February 25, 2025 04:14
@jira-pull-request-webhook
Copy link

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

@catamorphism catamorphism requested a review from srl295 February 25, 2025 04:14
@catamorphism catamorphism marked this pull request as ready for review February 25, 2025 04:14
@catamorphism catamorphism changed the title ICU-23059 Update spec tests, 2025-02-24 ICU-23059 Update spec tests Feb 25, 2025
@catamorphism catamorphism merged commit 0748442 into unicode-org:main Feb 25, 2025
101 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants