- From: Milber Ferreira via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Jun 2022 07:48:07 +0000
- To: public-design-tokens-log@w3.org
> Hmm, I'm not sure I see what the benefit would be. Kebab case is invalid syntax in just about every environment _except_ CSS, so to export names for JavaScript, iOS, Android, WinUI (and I imagine other stuff I'm not familiar with like Flutter and Qt), those names would have to be converted into something else. There's no possible naming standard that would be natural and valid in every different environment tokens would be used in, so I don't see how this would improve consistency other than maybe _slightly_ simplifying the renaming code for a conversion tool. Can you explain a little more about how you feel this would help? You're mixing things up here, I think. The `kebab` naming convention is not intended to distribute the tokens "as is", but rather to help tool makers have a consistent naming convention, which will increase debugging and make tools more accurate when converting to specific platforms or languages. Yes, *kebab* isn't supported in many languages, but it is supported in JSON. This is how we create powerful token taxonomies, so why not use it in the first place? As long as the token name field is left as "free form", we will hinder the User Experience of the tools being made since they may output repeated tokens (which may overwrite other tokens, etc.). -- GitHub Notification of comment by reblim Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/142#issuecomment-1165301645 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 June 2022 07:48:09 UTC