Jan Six
Jan Six
We should optimize the plugin's logic on startup as it's grown quite a bit over time and could use a refactor.
Given I have the following JSON ``` { "typography": { "regular": { "value": { "fontFamily": "Inter", "fontWeight": "16", "lineHeight": "24", "fontSize": "24", "letterSpacing": "16" }, "type": "typography" }, "alias": {...
Currently when we import typography styles we import references to atomic tokens with the old `$` notation. We should update that to use the preferred `{alias}` notation.
The W3C Spec outlines inheritance for types at a group level. Meaning, the following JSON produces tokens of type color: ### Ability to define types at a group-level ``` {...
Trying to rename `Text.PrimaryButton` in this JSON to `Text.Primary.Button` currently works and creates a broken UI, as we're effectively allowing the user to nest a token. ``` { "Text": {...
When users set their plugin window to a lower size and are using URL storage, sync provider options tend to have a long URL, which causes the UI to feel...
To better parse tokens when looking at the JSON tab of the plugin code editors typically offer syntax highlighting. It would be really helpful to have the same. Ideally, we...
We'll need to introduce a way for users to define what version of the spec they want to use, as I expect there to be breaking changes that will be...
We currently show tokens as they were applied, both in Inspect and when creating annotation layers. We should use a certain specified order so that it's easier to predict where...