Jan Six

So, to clarify, both should work, correct? ``` { "shadow": { "core": { "value": { "x": "0", "y": "1", "blur": "2", "spread": "0", "color": "{color.core.black.8}", "type": "dropShadow" } }, "alias":...

Would you want to mix aliases with regular shadows? I'm mainly thinking about keeping the UI clean here, technically it should be possible. As in ``` shadow: [ '{shadow.small}', {...

I would say this should be possible! I'm not sure what would be required, but I guess it would be split up into GET URL and POST URL. GET is...

Changed description to indicate a new approach that would let us keep using the `border` property for both the old way of applying border-color and also the new of applying...

This is in the plugin already, although not configurable! The plugin will currently convert rem by * 16, so 1rem = 16px. I'm wondering where/how we'd want to make this...

> Do I need the Pro version to use the GitHub sync feature? The person owning the repo uses a Pro Plan. Could it be that using Pro features is...

This is unfortunately a known limitation for now and is also affecting all other tokens. The plugin currently only works with one fill, not multiple. We have been talking about...

Yes, there's still a limitation in place in the plugin. You can only import fills with a single fill. There will be initial support for multiple box shadows in V68...

Oh good point! But we couldn't do anything for solid fills, could we?

As multiple boxShadows will be coming in V69 I'm changing title here to reflect that only fills are left (but those are not being done in V69)