Fix parsing of < after object literals with the jsx plugin
#14557
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
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/51934/ |
nicolo-ribaudo
approved these changes
May 17, 2022
nicolo-ribaudo
added
PR: Bug Fix 🐛
|
Rebased on top of #14558 |
existentialism
approved these changes
May 17, 2022
nicolo-ribaudo
changed the title
< after object literals with the jsx plugin
github-actions
bot
added
the
outdated
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When parsing
({}<x)with jsx plugin, Babel incorrectly marks<xas a jsxTagStart token. In token definitions we have}'sbeforeExprset totrue, which then causesstate.canStartJSXElementbetruein theupdateContexthook. In this PR we explicitly setstate.canStartJSXElementto betrueimmediately before}is consumed as the boundary between JS expression and jsx elements. Now in the({}<x), the<token after}can be correctly tokenized astt.ltbecause it is parsed within normal JS routines.