-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
chore(examples/theme-ui): fix styling #3949
chore(examples/theme-ui): fix styling #3949
Conversation
|
Hi @scottybrown, Welcome, and thank you for contributing to Remix! Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once. You may review the CLA and sign it by adding your name to contributors.yml. Once the CLA is signed, the If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected]. Thanks! - The Remix team |
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
f963900
to
ee6af24
Compare
This fix involves using |
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.
Thank you!
Co-authored-by: scottybrown <[email protected]>
Co-authored-by: scottybrown <[email protected]>
We expect the theme-ui example's pages to have a stark blue background, to demonstrate that the theme-ui theme is being applied.
Instead, it has no styling at all.
The cause is this PR, which removes some lines which are fundamental to how theme-ui works.
I have also removed 2 entries from a
useEffect
dependency array which were also added in the mentioned PR, which were causing repeatedMaximum update depth exceeded
to appear in the browser console. This does not seem to affect this example, but can cause UI hangs on apps with state.I've been unsuccessful in running linting against this example, so I can't verify whether my changes have brought back lint warnings. But they've certainly made the example more useful :)
Testing Strategy:
/
and/jokes
/maximum update depth exceeded
does not repeatedly appear in browser console