Description
Description
Some syntax and structural changes to the src JSON files are needed to facilitate long-term token maintenance through Tokens Studio. Provided that we can modify the build process to account for these changes, no major changes to the final list of tokens are anticipated. At most, we may need to alter the unit types of some niche values, but there will be no visual changes.
Proposed Advantages
This is the final step in setting us up to manage all of Calcite's core and semantic tokens in Tokens Studio (for both Figma and code!)
Which Component
No components should be affected, but if we end up changing values like 100% to 9999px for --calcite-corner-radius-pill, then we will want to confirm that all components using these tokens are unaffected visually.
Relevant Info
No response
Calcite package
- @esri/calcite-components
- @esri/calcite-components-react
- @esri/calcite-design-tokens
- @esri/calcite-ui-icons
- @esri/eslint-plugin-calcite-components
monday.com sync: #9059780039