Skip to content
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

Merged
merged 2 commits into from Apr 8, 2022

Conversation

valentinpalkovic
Copy link
Contributor

@valentinpalkovic valentinpalkovic commented Apr 7, 2022

Fixes "pseudo class potential unsafe warning" issue mentioned here: #17831 (comment)

What I did

How to test

  • Is this testable with Jest or Chromatic screenshots?
  • Does this need a new example in the kitchen sink apps?
  • Does this need an update to the documentation?

If your answer is yes to any of these, please make sure to include it in your PR.

@nx-cloud
Copy link

nx-cloud bot commented Apr 7, 2022

☁️ Nx Cloud Report

CI 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 target

Sent with 💌 from NxCloud.

Copy link
Member

@shilman shilman left a 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?

@shilman shilman changed the title fix: Pseudo class potential unsafe warning UI: Pseudo class potential unsafe warning Apr 7, 2022
Copy link
Contributor

@Andarist Andarist left a 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)

@shilman shilman merged commit 7366e9b into next Apr 8, 2022
@shilman shilman deleted the fix-pseudo-class-potential-unsafe-warning branch April 8, 2022 01:47
m7kvqbe1 added a commit to Royal-Navy/design-system that referenced this pull request May 13, 2022
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.
m7kvqbe1 added a commit to Royal-Navy/design-system that referenced this pull request May 13, 2022
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.
m7kvqbe1 added a commit to Royal-Navy/design-system that referenced this pull request May 16, 2022
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants