-
Notifications
You must be signed in to change notification settings - Fork 843
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
[CSS-in-JS] Expand use of @emotion/cache
#5831
Conversation
Preview documentation changes for this PR: https://eui.elastic.co/pr_5831/ |
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.
🙌 Glad the fix was this simple. I double checked both className
and css
override methods and in all 3 major browsers. Just a couple questions.
Co-authored-by: Caroline Horn <549577+cchaos@users.noreply.github.com>
Preview documentation changes for this PR: https://eui.elastic.co/pr_5831/ |
Preview documentation changes for this PR: https://eui.elastic.co/pr_5831/ |
Flaky Cypress test jenkins test this |
Preview documentation changes for this PR: https://eui.elastic.co/pr_5831/ |
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.
Changes LGTM; pulled & tested locally, I really like how EuiProvider cleaned up 👍
Preview documentation changes for this PR: https://eui.elastic.co/pr_5831/ |
Summary
Previously only global styles made use of the custom insertion point for
@emotion
styles via the@emotion/cache
CacheProvider
. Based on observations in Kibana, it will be beneficial to move all EUI@emotion
styles to into the same insertion location.We still ask that consumers configure this based on how their application is setup.
Checklist