🧑‍💻 JSON view/edit enhancements

When working in the JSON editor, the community has requested we explore some new functionality

• Understanding how editing the JSON might impact the way tokens are mapped

  • allow for remap to avoid broken tokens when possible (linter)

• Find and replace feature in JSON is limited to the current selected JSON file. It would be nice to know where else in the Token Project the keyword exists to speed up the workflow when maintaining Tokens and introducing mass changes to Token Names.

• Improve the behaviour of the JSON file when flipping back and forth between the no-code and JSON views

  • Today, the JSON scroll position resets, and if the token set is long, it requires a lot of scrolling to find the token you were previously looking at.

• Improve the color scheme for JSON view

  • Today a more colorful view flashes on the screen on open, then switches to a less colorful UI

• Highlight broken aliases in JSON mode

  • When viewing the tokens in JSON mode, it would be great if broken aliases are highlight text to give parity with the list view. A clear red background highlight on the text or squiggly underline in a color would be a sufficient indicator

  • If I edit in the JSON view, I have a hard time figuring out where the errors are that prevent me from editing it.

  • Today the only way to know there are broken references is when an Engineer communicates the issue from their side or Style Dictionary identifies the issue.

💭 How might we...

Support the people comfortable using the JSON editor within the plugin with some of the quality-of-life requests they are used to in other code editing programs.

💬 Feedback that is valuable

• How does this issue impact your day-to-day workflow?

• What workarounds do you have?

↔ Related topics

• 💡🎨🧑‍💻 JSON enhancements for color tokens → Jump to post