-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
UI: Pseudo class potential unsafe warning #17911
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit b35d409. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
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.
LGTM! @ndelangen @Andarist any thoughts?
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.
LGTM. Although I'm wondering why this wasn't creating a warning before (as it should)
The Storybook app currently throws some `console.errors`. These are warnings from the Emotion library. storybookjs/storybook#17911 storybookjs/storybook#6998 They have been working to resolve them upstream but don't appear to have caught all of them.
The Storybook app currently throws some `console.errors`. These are warnings from the Emotion library. storybookjs/storybook#17911 storybookjs/storybook#6998 They have been working to resolve them upstream but don't appear to have caught all of them.
The Storybook app currently throws some `console.errors`. These are warnings from the Emotion library. storybookjs/storybook#17911 storybookjs/storybook#6998 They have been working to resolve them upstream but don't appear to have caught all of them. Skipping this test until the underlying upstream issue is resolved.
Fixes "pseudo class potential unsafe warning" issue mentioned here: #17831 (comment)
What I did
How to test
If your answer is yes to any of these, please make sure to include it in your PR.