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.
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
Babel plugin JSX: Implement Fragment handling #15120
Babel plugin JSX: Implement Fragment handling #15120
Changes from all commits
6f5fa88
13a2d6f
635798d
1ec0ebf
c6ae6b4
36faddf
9e13d18
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So a consumer must opt in to this? Can there not be a default, like there is with
@babel/plugin-transform-react-jsx
?Is the expected behavior when this is
null
to not do anything when it encounters a fragment?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think
null
matches the default expectations across the board. When it'snull
and<></>
Fragments are encountered, no named import is added. However, this is JSX so thescopeVariable
will be added.If we consider the defaults (they could be omitted here):
Note that
pragmaFrag
's default isReact.Fragment
. With default arguments,<>In a Fragment</>
will result in something like:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh! That's quite tricky to follow, but it makes sense. Thanks for explaining.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain why this was changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I noticed that without this change, the following test fails (added in this PR):
It seems that
JSX
is an alias for most or all JSX that may be encountered.It seems that
<></>
should cause the import to be added.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re: Abbreviations. I suppose part of the purpose is in inheriting the Babel option by the same name?
https://babeljs.io/docs/en/babel-plugin-transform-react-jsx#pragmafrag
A bit unfortunate naming. I guess I'd rather be consistent than avoid the abbreviation, though.