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-22908 MF2: Update spec tests and update implementation for recent spec changes #3198

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

catamorphism
Copy link
Contributor

@catamorphism catamorphism commented Sep 21, 2024

Updating the spec tests requires two implementation changes:

Checklist
  • Required: Issue filed: https://unicode-org.atlassian.net/browse/ICU-22908
  • Required: The PR title must be prefixed with a JIRA Issue number.
  • Required: The PR description must include the link to the Jira Issue, for example by completing the URL in the first checklist item
  • Required: Each commit message must be prefixed with a JIRA Issue number.
  • 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
Copy link
Contributor Author

Note: this PR updates the shared tests, but doesn't update the ICU4J implementation with the two spec changes, so ICU4J tests will fail in CI for now.

I'll check with @mihnita about the Java side.

@mihnita
Copy link
Contributor

mihnita commented Sep 21, 2024

We also have this new fresh issue filed:
https://unicode-org.atlassian.net/browse/ICU-22906

I am almost tempted to separate the tests again...

@mihnita
Copy link
Contributor

mihnita commented Sep 21, 2024

I am tempted to say "let's drop it"

We were supposed to be code freeze, and this is something that my superstition feels very strongly: submit on Friday evening :-)

Even if it lands on Monday, it is still "Friday afternoon" with respect to the ICU release schedule.

… spec changes

Updating the spec tests requires two implementation changes:
* Match on variables rather than expressions --
  see unicode-org/message-format-wg#877
* Require attribute values to be literals (if present) --
  see unicode-org/message-format-wg#894
@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • icu4c/source/test/intltest/messageformat2test_read_json.cpp is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

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