fix(transformer/arrow-function): handle unicode when capitalizing property name#7311
Merged
graphite-app[bot] merged 1 commit intomainfrom Nov 17, 2024
Conversation
Contributor
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. |
Member
Author
This was referenced Nov 16, 2024
Merged
CodSpeed Performance ReportMerging #7311 will not alter performanceComparing Summary
|
This was referenced Nov 16, 2024
b3abcff to
1c61f62
Compare
6ce1352 to
ddbe935
Compare
This was referenced Nov 16, 2024
Member
Merge activity
|
1c61f62 to
a92521d
Compare
Dunqing
pushed a commit
that referenced
this pull request
Nov 17, 2024
…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
overlookmotel
added a commit
that referenced
this pull request
Nov 17, 2024
…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
Base automatically changed from
11-16-refactor_transformer_arrow-function_generate_super_binding_name_take_str_and_traversectx_
to
main
November 17, 2024 10:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Previously was assuming property name starts with an ASCII character. If it started with a multi-byte unicode char,
&property[1..]would panic.