fix: Convert numbers to hexadecimal inside Unicode escape sequences #24
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.
Feel free to suggest a better comment that you feel comfortable with.
For simplicity, this PR doesn’t distinguish between Unicode and Unicode property escape sequences. It works by the fact that, among the currently allowed
LoneUnicodePropertyNameOrValue
, onlygc
,sc
andscx
start with a lowercase character and none of them are purelya
~f
. Don’t hesitate to close this PR if you would like to achieve this by separatingENCLOSED_TOKEN
toP_TOKEN
andU_TOKEN
instead.Only minimal test cases are written, I’d love it if you could take over and include more.