- From: Drew Powers via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Jan 2022 21:17:59 +0000
- To: public-design-tokens-log@w3.org
> Does it need to also specify the type of gradient (.e.g linear, radial, concial, etc.)? I do really like the proposal here, and I like the simplicity of having the gradient stops be universal, where you decide linear, radial, conical when generating code for a specific component (which in one part makes sense because a rotated gradient is still the same gradient). But there also seems like an opportunity here to make `linear-gradient,` `radial-gradient`, and `conic-gradient` their own types to fill in the missing data (which exist as a concept both in CSS and Figma). Overall I fear that people may just abuse `metadata` on gradients here and put all the missing parts in there, at which point distinct types would be more useful. I could go either way—one gradient type with stops only, or distinct gradient types with complete properties. -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/101#issuecomment-1012522942 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 January 2022 21:18:01 UTC