- From: Drew Powers via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Jan 2025 16:30:15 +0000
- To: public-design-tokens-log@w3.org
> As a tool author, it is very difficult to reliably tell if a given spec is a single file vs. multi file with remote refs. I don't work with JSON Schema enough but there's enough prior art that I could find easily find a solution within 5 minutes so this looks pretty good. That’s a great point, and it is a little bit of a papercut for sure—you don’t always know the depth of schemas that refer to other schemas until you try resolving it. But this is also a common problem that has over a decade of prior art and workarounds, too, so it’s not new. This goes beyond this PR, but in many setups today, people _are_ already using multiple token files for their design system. And they have to manage and describe that “meta” layer that determines how everything fits together. By using JSON pointers (`$ref`s), some people MAY want to just have a single document that describes their entire token structure, and offload maintaining/building that meta layer. This gives them the option to do so. Of course, there are also more complex usecases with modes, etc., that will be solved by the still-in-progress Resolver proposal (that I have seen a preview, and am a big fan of!). So if we accept JSON pointers, we don’t require people to use multiple documents at all. We just give people better options to organize tokens in a way that works best for them without guiding them toward complexity or a self-contradictory design. -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/259#issuecomment-2590469384 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 January 2025 16:30:15 UTC