Open beauroberts opened 5 years ago
I like it. I'm going to prioritize deprecation warnings before this story.
"avatar.extraSmall": {},
"avatar.extraLarge": {},
"spacings.extraExtraSmall": {},
"spacings.extraSmall": {},
"spacings.small": {},
"spacings.medium": {},
"spacings.large": {},
"spacings.extraLarge": {},
"spacings.extraExtraLarge": {},
becomes...
"avatar.xSmall": {},
"avatar.xLarge": {},
"spacings.xxSmall": {},
"spacings.xSmall": {},
"spacings.small": {},
"spacings.medium": {},
"spacings.large": {},
"spacings.xLarge": {},
"spacings.xxLarge": {},
Do you support aliasing as distinct from referencing in your design language?
If we were to do it ourselves we'd just do something like:
'spacings.xSmall': {
value: {
ref: 'spacings.extraExtraSmall',
},
},
I suppose there's a chance that they could become out of sync if someone chose to override the value of xSmall
but not extraExtraSmall
, but for us at least I don't really see that happening in practice.
Hello - an dev ergonomics request! Would it be possible to add more terse aliases for spacing/sizing values, e.g.
extraExtraSmall
=>xxSmall
. We were thinking of adding this in our layer but thought we'd ask if other devs would also prefer something that requires a bit less typing.