fix: Filter out action tokens from generated variables.css (#141)

`--cnvs-brand-action-**` tokens where always created and added to `variables.css`. When we consume these tokens in Canvas Kit, that token is **always** known, meaning the fallback of `--cnvs-brand-primary-**` would never get hit, breaking theming. This PR filters out the action tokens from out generated css files so that we can allow cascading of our actions tokens through the CanvasProvider. [category:Tokens] Release Note: Removing `cnvs-brand-action-**` tokens to ensure proper cascading. These tokens won't be part of `variables.css`. Co-authored-by: manuel.carrera <[email protected]>
Workday · Feb 6, 2025 · 370f902 · 370f902
1 parent 0da45e6
commit 370f902
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/packages/canvas-tokens/build.ts b/packages/canvas-tokens/build.ts
@@ -25,6 +25,7 @@ const config = setConfig({
           level: ['brand', 'sys'],
           format: 'merge/refs',
           combineWith: ['{platform}/composite', '{platform}/variables', '{platform}/shadow'],
+          filter: filters.filterActionTokens,
           options: {
             outputReferences: true,
           },

diff --git a/packages/canvas-tokens/utils/filters/index.ts b/packages/canvas-tokens/utils/filters/index.ts
@@ -62,3 +62,8 @@ export const filterCodeTokens: Matcher = token => {
   const excludedTokens = ['level', 'shadow', 'typescale'];
   return !excludedTokens.includes(token.path[1]);
 };
+
+export const filterActionTokens: Matcher = token => {
+  const excludedTokens = ['action'];
+  return !excludedTokens.includes(token.path[1]);
+};