Sync Figma variables to tokens #69
sync-figma-to-tokens.yml
on: schedule
sync-figma-to-tokens
1m 17s
Annotations
1 error and 1 warning
sync-figma-to-tokens
Unexpected error: .husky/pre-commit: 4: Bad substitution
.husky/pre-commit: 5: Bad substitution
..Running design token checks
> [email protected] paddingY:verify
> tsx src/scripts/verify-paddingY.ts
🛑 button.large.secondary: 7 does not match 8. Run paddingY:update if this change is expected.
🛑 button.xlarge.secondary: 19 does not match 20. Run paddingY:update if this change is expected.
🛑 component.xsmall: 3 does not match {base.static.spacing.xxsmall}. Run paddingY:update if this change is expected.
🛑 component.small: 3 does not match {base.static.spacing.xxsmall}. Run paddingY:update if this change is expected.
🛑 component.large: 8 does not match {base.dimension.225}. Run paddingY:update if this change is expected.
🛑 component.xlarge: 20 does not match {base.dimension.500}. Run paddingY:update if this change is expected.
> [email protected] build
> rm -rf ./dist && yarn build-style-dictionary
yarn run v1.22.22
$ tsx src/scripts/build-style-dictionary.js
js
✔︎ dist/esm/base.js
js/cjs
✔︎ dist/cjs/base.cjs
css
✔︎ dist/css/base.css
docs
✔︎ dist/docs/base.js
js
✔︎ dist/esm/global.js
js/cjs
✔︎ dist/cjs/global.cjs
css
⚠️ dist/css/global.css
While building global.css, filtered out token references were found; output may be unexpected. Here are the references that are used but not defined in the file
color.focus
base.dimension.50
This is caused when combining a filter and `outputReferences`.
docs
✔︎ dist/docs/global.js
js
✔︎ dist/esm/color.dark.js
js/cjs
✔︎ dist/cjs/color.dark.cjs
css
⚠️ dist/css/color.dark.css
While building color.dark.css, token collisions were found; output may be unexpected.
Output name hpe-color-decorative-green was generated by:
color.decorative.green #008567
color.decorative.green! #01a982
Output name hpe-color-decorative-purple was generated by:
color.decorative.purple #6633bc
color.decorative.purple! #7630ea
Output name hpe-color-decorative-teal was generated by:
color.decorative.teal #117b82
color.decorative.teal! #00e8cf
Output name hpe-color-decorative-blue was generated by:
color.decorative.blue #00739d
color.decorative.blue! #00739d
Output name hpe-color-decorative-red was generated by:
color.decorative.red #a2423d
color.decorative.red! #c54e4b
Output name hpe-color-decorative-orange was generated by:
color.decorative.orange #9b6310
color.decorative.orange! #ff8300
Output name hpe-color-decorative-yellow was generated by:
color.decorative.yellow #8d741c
color.decorative.yellow! #fec901
This many-to-one issue is usually caused by some combination of:
* conflicting or similar paths/names in property definitions
* platform transforms/transformGroups affecting names, especially when removing specificity
* overly inclusive file filters
While building color.dark.css, filtered out token references were found; output may be unexpected. Here are the references that are used but not defined in the file
base.color.white.opacity6
base.color.grey.1300
base.color.white.opacity7
base.color.grey.1200
base.color.grey.1100
base.color.black.opacity12
base.color.red.800-Opacity30
base.color.blue.400-Opacity12
base.color.yellow.400-Opacity12
base.color.brand
base.color.green.1000
base.color.green.900
base.color.green.600
TBD
base.color.green.500-Opacity30
base.color.white.opacity72
base.color.white.opacity36
base.color.white.opacity12
base.color.white.100
base.color.white.opacity50
base.color.white.opacity20
base.color.white.opacity24
base.color.red.750
base.color.blue.700
base.color.green.700
base.color.orange.700
base.color.grey.700
base.color.purple.900
base.color.teal.700
base.color.red.850
base.color.yellow.700
base.color.purple.800
base.color.teal.400
base.color.orange.500
base.color.yellow.400
base.color.black.opacity36
base.color.black.opacity50
|
sync-figma-to-tokens
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/checkout@v3, peter-evans/create-pull-request@v5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|