Skip to content

Commit 8ded18f

Browse files
committed
docs: drop the missing-token section
The comments it describes are stripped from the generated tables and do not survive minification into dist, so a reader of the docs has no way to encounter them.
1 parent 74751d6 commit 8ded18f

1 file changed

Lines changed: 0 additions & 11 deletions

File tree

apps/docs/src/content/docs/ui-library/design-tokens.mdx

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -73,14 +73,3 @@ The CSS is rebuilt from `tokens.json` whenever the package is built - on
7373
```sh
7474
pnpm --filter @workflowbuilder/ui-tokens build
7575
```
76-
77-
## A note on "missing token" comments
78-
79-
Some component variables in the source carry a `/* missing token */` comment -
80-
a marker from the design-system port meaning "no matching design token existed
81-
at the time, so this holds a literal value (or a stand-in token)". The export
82-
has grown since, and several of the referenced tokens now exist, so treat the
83-
comment as a historical hint rather than a statement about the current
84-
`tokens.json`. The flagged variables are ordinary `--ax-public-*` override
85-
points either way, and the comments are stripped from the generated CSS
86-
variables tables.

0 commit comments

Comments
 (0)