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

Selector specificity issue when migrating from styled-components #607

Open
benskz opened this issue Mar 20, 2025 · 0 comments
Open

Selector specificity issue when migrating from styled-components #607

benskz opened this issue Mar 20, 2025 · 0 comments

Comments

@benskz
Copy link

benskz commented Mar 20, 2025

We're currently in the process of migrating to goober from styled-components and I was wondering if anyone else has run into this same issue.

When using styled-components, our styles are applied to elements with a double class selector (.btZBKL.btZBKL for example). As we've built our app with this in mind, after migrating to goober which only uses one class selector, component styles no longer have high enough specificity and are overriden by other styles.

I don't see this as an issue with goober but any thoughts are appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant