-
-
Notifications
You must be signed in to change notification settings - Fork 458
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
fix(transformer/arrow-function): handle unicode when capitalizing property name #7311
fix(transformer/arrow-function): handle unicode when capitalizing property name #7311
Conversation
Your org has enabled the Graphite merge queue for merging into mainAdd the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
CodSpeed Performance ReportMerging #7311 will not alter performanceComparing Summary
|
b3abcff
to
1c61f62
Compare
6ce1352
to
ddbe935
Compare
Merge activity
|
1c61f62
to
a92521d
Compare
…perty name (#7311) Previously was assuming property name starts with an ASCII character. If it started with a multi-byte unicode char, `&property[1..]` would panic.
ddbe935
to
50c18c7
Compare
a92521d
to
7fc8905
Compare
…perty name (#7311) Previously was assuming property name starts with an ASCII character. If it started with a multi-byte unicode char, `&property[1..]` would panic.
50c18c7
to
c4d5c2d
Compare
…perty name (#7311) Previously was assuming property name starts with an ASCII character. If it started with a multi-byte unicode char, `&property[1..]` would panic.
7fc8905
to
5cfe0b6
Compare
c4d5c2d
to
389b84e
Compare
Previously was assuming property name starts with an ASCII character. If it started with a multi-byte unicode char,
&property[1..]
would panic.