-
Notifications
You must be signed in to change notification settings - Fork 12
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
Update to Unicode v16.0.0 #92
Conversation
I recall that I manually paste the emoji results into the fixtures and it was not very smooth. Yes, a "rebaseline test fixtures" script will definitely help the situation.
|
2cc144a
to
1571fa5
Compare
@@ -2,10 +2,25 @@ const TRANSFORM_U = { unicodeFlag: 'transform', unicodeSetsFlag: 'transform' }; | |||
|
|||
const Basic_Emoji = { | |||
get all() { return `${this.strings}|[${this.chars}]` }, | |||
// node -e "process.stdout.write(require('regenerate-unicode-properties/Property_of_Strings/Basic_Emoji').strings.sort((a,b)=>b.length-a.length).join('|'))" |
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.
Provided node oneliners to update the test fixtures. Personally I piped the result to pbcopy
and paste directly in the IDE. At least we can do it semi-manually.
We also restructured the RGI_Emoji tests so that we can easily update the result every year.
@mathiasbynens This PR is ready to review now. |
Thanks @JLHwung! |
test/fixtures
must be rebaselined before this can be merged.@JLHwung Do you remember how you did this for #84? Maybe we should check in a “rebaseline test fixtures” script to more easily update expectations as part of future Unicode updates.