Update Figma variables from JSON files #1884
Conversation
| branches: | ||
| - production | ||
| paths: | ||
| - "tokens/movistar.json" |
There was a problem hiding this comment.
I think you can use something like "tokens/**.json" or similar. This will prevent you from having to update this in the future by hand (https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)
There was a problem hiding this comment.
Thinking about this, if we for example add a new skin but we dont want to sync it with figma via script yet, the action will trigger when changes on that JSON are made, how we can avoid this?
There was a problem hiding this comment.
If we add a new skin and we dont want to sync with Figma, just don't include as a "available" skin in .mjs script
There was a problem hiding this comment.
At the end, we will keep "paths" for each brand.json file to avoid run the script with unofficial .json files
Description
This feature allows the creation of figma variables by running a script in the repository.
https://www.tldraw.com/s/v2_c_snnVQbmyyGW4BzwXyXPwZ?d=v6816.-947.4025.2072.page
This script should:
paletteen each skin fileModeandBrandin a middleware fileThis middleware file is the one that will be used to link variables in all Mistica components
Each collection will appear as a selector in the UI:
Appart from the tokens defined in JSON files, we need to create figma-oriented tokens:
Test file with variables created:
https://www.figma.com/design/wlnMwpneZheC7CskSJAw4g/Middleware-POST-test-V2?node-id=0-1&node-type=canvas&t=scPU5BKt3mgO0tCf-0