feat: design system tokens#172
Merged
Merged
Conversation
johnthecat
approved these changes
May 26, 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
2 participants
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.
Summary
Rename the
ColorTokenandTypographyStyleSCALE codec strings inpackages/host-api/src/protocol/v1/customRenderer.tsto match the new Polkadot design system token paths.TypographyStyle
titleXLheadline.largeheadlinetitle.medium.regularbodyMbody.large.regularbodySbody.medium.regularcaptionbody.small.regularColorToken
textPrimaryfg.primarytextSecondaryfg.secondarytextTertiaryfg.tertiarybackgroundPrimarybg.surface.mainbackgroundSecondarybg.surface.containerbackgroundTertiarybg.surface.nestedsuccessfg.successerrorfg.errorwarningfg.warningWire compatibility
Variant order is preserved, so SCALE binary encoding (which is ordinal-positional) is unchanged — any payload encoded against the old strings decodes identically against the new ones.
What does change is the symbolic string surfaced at every typed boundary: the TypeScript literal-union types accepted by
Text/Modifier/etc. now use the new names. Any product script that passed string literals likestyle="caption"orcolor="textPrimary"will fail to type-check and must be updated to the new identifiers.