fix(parser): fix additional char being consumed in JSXText #259
Conversation
This file contains 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
yesmeck
commented
Apr 5, 2023
yesmeck
force-pushed
the
fix-jsx-text
branch
2 times, most recently
from
816a76f
to
78a2158
Compare
|
How did you find this? Can I know what you are working on with oxc 😁 You can remove the test by the way. It's all good if |
|
I was trying oxc lint on some random projects. Actually I found this bug when I was debugging another bug. |
|
Thank you for the contribution @yesmeck ! |
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.
In its current implementation, the first char of a JSXText will be lost.