Add figma.commitUndo() points for token operations #3607
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds
figma.commitUndo()
calls at key points where tokens are applied to or removed from Figma layers, enabling users to use Figma's native undo (Cmd/Ctrl+Z) to revert token operations in logical chunks.Problem
Previously, when users applied or removed design tokens, there were no undo points created in Figma's history. This meant that using Figma's native undo would either not work or would undo unrelated operations, making it difficult to experiment with tokens or correct mistakes.
Solution
Added strategic
figma.commitUndo()
calls before major token operations:Implementation Details
All
figma.commitUndo()
calls are guarded with proper checks:This ensures compatibility with test environments where the Figma API may not be available.
The implementation creates undo points at the right granularity level - one per high-level user action rather than per individual property or node, preventing excessive undo points that would make the undo history difficult to navigate.
Files Modified
setValuesOnNode.ts
- Main token application functionasyncMessageHandlers/removeTokensByValue.ts
- Token removal operationsasyncMessageHandlers/update.ts
- Bulk update operationsasyncMessageHandlers/setNodeData.ts
- Node data updatesasyncMessageHandlers/swapStyles.ts
- Style swapping between themesasyncMessageHandlers/remapTokens.ts
&bulkRemapTokens.ts
- Token remappingasyncMessageHandlers/setNoneValuesOnNode.ts
- Setting none valueslivingDocumentation/applyTokens.ts
- Living documentation token applicationTesting
User Impact
Users can now:
This significantly improves the user experience when working with design tokens in the plugin.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
https://api.github.com/repos/tokens-studio/tokens-studio%2Ffigma-plugin/languages
/home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js
(http block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.