-
-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unusual Remapping (Renaming) Behaviour #2338
Labels
Comments
This bug seems to be back. If via the JSON editor I:
In the inspect panel I can see they haven't remapped and that I have to manually remap them from CleanShot.2024-04-29.at.16.24.57.mp4 |
This is reproducible as of rc10 |
@six7 still present in |
@keeganedwin I dont understand the issue description, can you try to rephrase or create a 1min video explaining it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When remapping (changing path name) certain tokens, they usually get added to other token-types. I was editing my Font type tokens, deleting and remapping to typography. When I checked the inspect tab to double check the tokens applied, the font+typography naming where prefixed with the padding tokens.
Here is the used-case of a user facing the same issue:
Expected behavior
Plugin shouldn't remap tokens into other token-types.
Screenshots or Screencasts
I have annotated the groups and the
incorrect prefixed
token names inRed
User screenshots:


User Recording:
User renames one group from
Utrecht
toTodo
, but upon confirming the remap process all other tokens are renamed as wellhttps://github.com/tokens-studio/figma-plugin/assets/93133012/e70e95d2-275e-43ef-b073-b4f1db7efee5
The text was updated successfully, but these errors were encountered: