feat(linter): Improve format check in linter#2538
Merged
aweell merged 7 commits intoproductionfrom Feb 17, 2026
Merged
Conversation
yceballost
reviewed
Feb 9, 2026
yceballost
reviewed
Feb 11, 2026
yceballost
approved these changes
Feb 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Description: Improve Format Check in Linter
This pull request enhances the linter's functionality by introducing two distinct validation modes: format and contrast.
Motivation
The primary motivation behind this change is to improve the validation process for design tokens by providing clear and targeted checks. Previously, the linter was limited in its ability to validate token descriptions against palette references and ensure compliance with WCAG contrast standards. This update allows for a more structured approach to validation, enabling developers to focus on specific aspects of their tokens.
Key Improvements
Format Mode: This mode checks for:
Contrast Mode: This mode checks for:
Enhanced User Experience: The command-line interface has been updated to prompt users for the desired validation mode, making it easier to use the linter effectively without needing to remember specific command-line arguments.
Error Reporting: The linter now provides detailed error messages for both description mismatches and contrast failures, along with suggestions for alternative colors that meet contrast requirements.
By implementing these changes, this pull request significantly enhances the robustness of our linter, ensuring that our design tokens are both accurately described and compliant with accessibility standards. This ultimately leads to a more consistent and accessible user experience across our applications.