- From: James Nash via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Dec 2021 21:06:59 +0000
- To: public-design-tokens-log@w3.org
@kevinmpowell Yeah, I wasn't too keen on adding the `gradient-stop` type myself. My thinking was as follows: In the composite type intro, we say that composite type values are either objects whose properties are sub-values, or they are an array of sub-values. Sub-values in turn are defined as a value from one of the types or a reference to a token of the same type. Therefore, having an array of objects which themselves are _not_ sub-values, but whose properties _are_ doesn't quite fit that definition. Breaking it up into 2 types gets around that. But... it's klunky. So, I'll have a go at rewording our definition of composite types so that it's broader. Then I can get rid of `gradient-stop` as its own type. -- GitHub Notification of comment by c1rrus Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/86#issuecomment-992909801 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 December 2021 21:07:01 UTC