You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dimension type is a token that specifies a dimension, and is always bound to a specific unit (either rem or px).
As a dimension can be used in a wide range of applications, we need to rethink how we currently apply tokens. A user must choose on right-click what they want to apply this token for, like today but offering more choice.
Things to do
Introduce a new dimension type
Validate that values of this token are specified as either 24px or 24rem (or {alias} / $alias), if not, give an error message in the value: Value must include either px or rem
When right-clicking this token, let the user choose between properties for Spacing (all properties that we have in Spacing tokens), Sizing (all properties of Sizing tokens), borderWidth (all properties of borderWidth tokens)
When left-clicking this token, let's be smart: A) User has auto layout selected: Apply the Gap property, B) User has any other frame selected: Apply sizing, C) user has a mix selected: Apply Gap.
In order to support the upcoming W3C format we'll need to introduce a dimension type: https://second-editors-draft.tr.designtokens.org/format/#dimension
The dimension type is a token that specifies a dimension, and is always bound to a specific unit (either rem or px).
As a dimension can be used in a wide range of applications, we need to rethink how we currently apply tokens. A user must choose on right-click what they want to apply this token for, like today but offering more choice.
Things to do
dimension
type24px
or24rem
(or{alias}
/$alias
), if not, give an error message in the value:Value must include either px or rem
Spacing (all properties that we have in Spacing tokens)
,Sizing (all properties of Sizing tokens)
,borderWidth (all properties of borderWidth tokens)
This is an issue that will complete #289
The text was updated successfully, but these errors were encountered: