-
Notifications
You must be signed in to change notification settings - Fork 184
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
Datagen key file support and test scaffolding #1526
Conversation
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.
I like the choice of leaving in the test scaffolding for key-extract so it's easy to use this test later too
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.
I cross-referenced this with #1460. I noticed one thing missing and another thing that shouldn't have been deleted.
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
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.
I'm approving but please fix the messy diffs in build-test.yml. Only one change is required: adding
- name: Build Examples and test icu4x-key-extract
uses: actions-rs/[email protected]
with:
command: make
args: wasm-compare-worklog-keys
My PR also moved the Install Node.js up in the process, but this is unnecessary and could be done in a different, smaller PR.
This is adapted from #1460