Emotion: Custom instance to avoid global conflict #24
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
This update adjusts the (custom) Emotion namespace to avoid collision with potential stock instances of Emotion. Tests have been added for this case. A `emotion.cssWithScope` guard + fallback is added to `create-emotion-styled` that defaults to `emotion.css` if that custom function is not available.
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.
Emotion: Custom instance to avoid global conflict 👩🎤
This update adjusts the (custom) Emotion namespace to avoid collision with
potential stock instances of Emotion. Tests have been added for this case.
A
emotion.cssWithScopeguard + fallback is added tocreate-emotion-styledthat defaults to
emotion.cssif that custom function is not available.