-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST] Support filtering out token-sets (such as those "treated as source") #32
Comments
Style Dictionary has some generic approaches to how they handle it. Flutter impl. https://v4.styledictionary.com/examples/splitting-output-files/ |
The linked docs require a Figma login. |
Updated! |
I opened a PR specific to omitting "core" tokens #34. It could easily be modified to accept a list of paths for token sets to omit if that need arrises. |
💬 Description
If I mark a token-set as "source", it doesn't allow me to access those variables in Figma. Ideally it would work the same in the code.
If this is controversial, it would be great if there was a setting passed to the generator (or a config file) that allowed you to ignore certain token-sets. Or ignore
source
token-sets.❓ Link to specification or documentation (if available)
Tokens studio docs
Details
themes/semantic-light
references colors incore
, but they shouldn't be accessible in the code (to prevent people from using colors directly instead of through the semantic theme token set).In
$themes.json
there is this:The text was updated successfully, but these errors were encountered: