- From: Nico André via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Oct 2022 14:14:59 +0000
- To: public-design-tokens-log@w3.org
After some empirical implementations of the spec I ended up missing naming for more than files themselves. From a library and API editor perspective, I missed names for: - The JSON files as the core topic of this discussion 🎯 - when they exist — in file-system environments, compared to API or DB as exposed by @CITguy - I opted for "tokens file(s)" - The type declaration of the Design Tokens JSON Object that I would use for functions like: - `validateDesignTokens(tokens: ???)` — I opted for `DesignTokenTree` without conviction - The documentation of an API accepting this very same Design Tokens JSON Object - "Where the body of the request is a ???" — I opted for Design Token Tree just to match the previous I don't hold a strong opinion on any particular proposition made previously, but I think we must consider giving cohesive names to such close concepts. -- GitHub Notification of comment by nclsndr Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/164#issuecomment-1295054723 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 October 2022 14:15:01 UTC