Skip to content

Extended-tokens: Update to latest JSON spec and fix camel casing - #34439

Merged
Mitch-At-Work merged 7 commits into
microsoft:extended-tokensfrom
Mitch-At-Work:user/mifraser/update-tokens-and-linting
May 14, 2025
Merged

Extended-tokens: Update to latest JSON spec and fix camel casing#34439
Mitch-At-Work merged 7 commits into
microsoft:extended-tokensfrom
Mitch-At-Work:user/mifraser/update-tokens-and-linting

Conversation

@Mitch-At-Work

Copy link
Copy Markdown
Contributor

Previous Behavior

Token names were lowercased and then camelcased

New Behavior

Token casing is now important to keep, lowercase two unique scenarios (all caps)
fluentOverrides.ts now moved to src/fallbacks/fluentOverrides.ts
We now enforce alphebetical JSON key sort via linter to simplify merge conflicts
Update already merged token names that changed due to camel case update

@github-actions

Copy link
Copy Markdown

Pull request demo site: URL

@Mitch-At-Work
Mitch-At-Work marked this pull request as ready for review May 13, 2025 23:20
@Mitch-At-Work
Mitch-At-Work requested review from a team as code owners May 13, 2025 23:20

@brandonthomas brandonthomas left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, only thing is we need unit tests around this both to safe guard from name changes we import from Figma or configuration issues on our end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants