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

chore: extract icu-messageformat-parser test cases into their own test case files #3763

Merged
merged 2 commits into from
Sep 6, 2022

Conversation

pyrocat101
Copy link
Member

The test cases of icu-messageformat-parser are now in icu-messageformat-parser-tests folder that can be shared with a potential Rust implementation.

To update the mismatching parser result, run the test with UPDATE_SNAPSHOT=1 environment variable.

@longlho
Copy link
Member

longlho commented Aug 14, 2022

can you hold off merging until I migrate to rules_js? hopefully that'll be done in the next few days

@pyrocat101
Copy link
Member Author

sure

@pyrocat101 pyrocat101 force-pushed the parserTestCase branch 2 times, most recently from ab75aed to d5110f7 Compare August 20, 2022 20:24
@pyrocat101 pyrocat101 mentioned this pull request Aug 21, 2022
@github-actions
Copy link

github-actions bot commented Sep 5, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Sep 5, 2022
@longlho longlho changed the title chore: extract ICU messageformat parser test cases into their own test case files chore: extract icu-messageformat-parser test cases into their own test case files Sep 6, 2022
@longlho longlho merged commit 2ce29a2 into main Sep 6, 2022
@longlho longlho deleted the parserTestCase branch September 6, 2022 04:33
unional pushed a commit to unional/formatjs that referenced this pull request Jun 7, 2023
…t case files (formatjs#3763)

Co-authored-by: long.ho <long.ho@cloudkitchens.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants