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

Token coverage monitoring #3611

Open
schaertim opened this issue Oct 2, 2024 · 1 comment · May be fixed by #3714
Open

Token coverage monitoring #3611

schaertim opened this issue Oct 2, 2024 · 1 comment · May be fixed by #3714
Assignees

Comments

@schaertim
Copy link
Contributor

It might be helpful to have some way to keep track of the coverage of the tokens to make sure none are forgotten during implementation. Something working similarly to test coverage tools could be an option.

@gfellerph gfellerph added needs: discussion There is at least one topic in the pattern descussion meeting about the issue needs: 🏓 dev roundtable To be discussed at the roundtable of esteemed developers labels Oct 3, 2024
@gfellerph
Copy link
Member

Resolution: Create a script that compares component token names from the output (how to get to all component token names) and checks if they can be found in the styles and component packages (resolve the name according to mixin usage).

@gfellerph gfellerph added 📦 tokens and removed needs: discussion There is at least one topic in the pattern descussion meeting about the issue needs: 🏓 dev roundtable To be discussed at the roundtable of esteemed developers labels Oct 3, 2024
@gfellerph gfellerph added this to the Maintenance III milestone Oct 8, 2024
@schaertim schaertim self-assigned this Oct 9, 2024
@schaertim schaertim linked a pull request Oct 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🤬 Dev in review
Development

Successfully merging a pull request may close this issue.

2 participants