You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+69Lines changed: 69 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -455,6 +455,75 @@ run();
455
455
456
456
You can find a variation of this example [here](https://github.com/tokens-studio/lion-example). It outputs a CSS file for every theme combination _for every component_, e.g. `button-business-blue.css`, `date-picker-business-blue.css` and so on. This caters to use cases where component-level tokens as required, e.g. when implementing Web Components.
457
457
458
+
#### Single-file tokens example
459
+
460
+
> This is not recommended because it's a pretty complex workaround.
461
+
> The best method is to just migrate to multi-file tokens export.
462
+
463
+
The same full example as above but assuming single token-file export.
464
+
465
+
What it does is, take your single `"tokens.json"` file and turn it into multi-file by
466
+
persisting the sets as separate files in a `"tokens"` folder and then creating the SD config accordingly.
0 commit comments