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

fix(badge): css variables used as privately #188

Merged
merged 2 commits into from
Aug 5, 2022

Conversation

muratcorlu
Copy link
Contributor

As we discussed in #164, it was not possible to set badge CSS variables from upper levels of dom tree because default values set in :host selector. This was causing difficulties to style badge in tab component, because we use badge inside tab component's shadow dom and it's not possible to query badge inside tab in CSS. This makes CSS variables of badge component like a theme variables, so user can set those variables in any scope (badge component level, parent component level or document level).

@sonarcloud
Copy link

sonarcloud bot commented Aug 5, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@muratcorlu
Copy link
Contributor Author

@buseselvi I added 2 more stories to test small badge with icon (we hide icon in this case) and large badge with icon. Can you please check them on Chromatic?

@muratcorlu muratcorlu merged commit 9792746 into next Aug 5, 2022
@muratcorlu muratcorlu deleted the badge-css-property-arrangment branch August 5, 2022 11:16
@github-actions
Copy link

github-actions bot commented Aug 5, 2022

🎉 This PR is included in version 2.0.0-beta.17 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

github-actions bot commented Apr 6, 2023

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

3 participants