Closed jemiluv8 closed 2 weeks ago
Latest commit: af1cdfb750dde273ddc1952b04bb55074885bc8c
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
fixes #8560 /claim #8560
Summary
There was a class name conflict between two third party components
The react-command-pallete library comes with a default theme called "atom" that has a declaration for "atom-input" This theme is imported whenever the react-command-pallete is used and was thus globally available.
Our graphql variable "Type" also has the class name atom-input and therefore inherits the global styling for the default atom theme from the react-command-pallete component.
My proposed solution just overrides those styles by introducing a global declaration with higher specificity that unsets the css declaration. I';ve seen similar done for the atom-overlay class.
Default atom style from the command-pallete library.
This is imported as a global css by the library.
Fixed output
How did you test this change?
Click testing
Are there any deployment considerations?
No
Does this work require review from our design team?
No