Skip to content

Export js format from design-tokens #7986

Closed
@alisonailea

Description

@alisonailea

Check existing issues

Description

Add a new format to the transformer config that can be used for generating documentation on the Calcite docsite.

Acceptance Criteria

CI Verification

After #8050 is merged, output for the Calcite Design Tokens for each platform (including JS and ES6) can be observed and verified in the .snapshot files.

Local Verification

  1. checkout the branch locally
  2. run npm run build at root
  3. all build processess should pass
  4. observe calcite-design-tokens/dist now contains platform folders
  5. observe the platform folders include js and es6 folders which contain token files that are not empty and have the .js and .ts file extensions.
  6. These files align to the JSON spec

Relevant Info

https://amzn.github.io/style-dictionary/#/formats?id=javascriptmodule
https://amzn.github.io/style-dictionary/#/formats?id=typescriptmodule-declarations

Which Component

design-tokens

Priority impact

p3 - want for upcoming milestone

Calcite package

  • @esri/calcite-design-tokens

Esri team

Calcite (dev)

Metadata

Metadata

Labels

4 - verifiedIssues that have been tested, confirmed as mitigated, and are ready to close.Calcite (dev)Issues logged by Calcite developers.enhancementIssues tied to a new feature or request.estimate - 2Small fix or update, may require updates to tests.impact - p2 - want for an upcoming milestoneUser set priority impact status of p2 - want for an upcoming milestonep - highIssue should be addressed in the current milestone, impacts component or core functionality

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions