🧪 [SPIKE] Component-level tokens exploration #2471
Draft
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
(mainly coming from `Badge` apart from horizontal padding)
Not 100% exactly as it was before, visually, because of how the custom border/focus implementation for the different variants
didoo
force-pushed
the
spike-component-level-tokens-experiment
branch
from
f776c4d
to
db0346d
Compare
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.
🚨 DO NOT MERGE 🚨
📌 Summary
Branch used for exploring what is the impact of introducing full coverage for component-level tokens, in relation to theming (for dark/light mode, as well as to "emulate" other design languages).
👀 Comparisons
🔗 External links
Jira tickets: