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
fix: make styled-jsx/babel plugin respect the source type #684
fix: make styled-jsx/babel plugin respect the source type #684
Changes from all commits
4eb109d
0577121
0fae5a3
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.
I'm not 100% sure what will happen if there is an existing variable in scope that has the same name as
STYLE_COMPONENT
(_JSXStyle
), but I think theaddDefault
helper will modify thenameHint
to avoid a collision. Ideally, nonameHint
would be used and the automatic name of the injected default import would be used throughout the code instead of a hardcoded constant. This way a user could have a_JSXStyle
variable name in the same scope, no problem.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.
All code branches that call this already check if
STYLE_COMPONENT
is in scope, so this should "just work".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.
There is a remote chance that
_JSXStyle
is in the source code but it is not styled-jsx's i.e. the user defined a binding with that name which will conflict withSTYLE_COMPONENT
.If you want to fix this, you should probably generate a unique identifier from
STYLE_COMPONENT
, put it in state and pass it to helpers if necessary but I probably I wouldn't bother in this PR – it's been like that for 5-ish years