The Problem with Renaming Collections and Modes

Oct 13, 2025 by leolavanderia.com.br 140 views

Understanding the Issue

The release of #3260 has introduced a critical bug in the plugin, affecting users who have already imported variables. When a user renames a collection or mode and imports the changes, the plugin fails to update the existing sets and themes. Instead, it creates a new folder, set, and theme-group, forcing users to reapply tokens. This behavior is not only frustrating but also time-consuming, especially for users with complex setups.

The Problem with Renaming Collections and Modes

Let's consider a scenario where a user has a setup like Primitives/default. They rename the collection and mode to Primitive/main in Figma and import the changes. The plugin, however, doesn't recognize the existing sets and themes and creates a new one. This means that users have to reapply tokens, which can be a tedious process, especially for large and complex designs.

The Expected Behavior

The expected behavior is that the plugin should update the existing sets and themes when a user renames a collection or mode. This would ensure that the changes are reflected correctly, and users don't have to reapply tokens. The plugin should be able to recognize the existing sets and themes and rename them accordingly, rather than creating a new one.

Steps to Reproduce the Behavior

To reproduce the behavior, follow these steps:

Step 1: Import a Collection and a Mode

Import a collection and a mode into the plugin. This will create a new folder, set, and theme-group.

Step 2: Rename the Collection and Mode

Rename the collection and mode in Figma. For example, rename Primitives/default to Primitive/main.

Step 3: Import the Changes

Import the changes into the plugin. The plugin should update the existing sets and themes.

Step 4: See the Error

However, the plugin fails to update the existing sets and themes and creates a new one. This means that users have to reapply tokens, which is not the expected behavior.

Screenshots and Screencasts

To better understand the issue, please refer to the following screenshots and screencasts:

Conclusion

The plugin's failure to update existing sets and themes when a user renames a collection or mode is a critical bug that needs to be addressed. The expected behavior is that the plugin should update the existing sets and themes, rather than creating a new one. By following the steps outlined above, users can reproduce the behavior and understand the issue better. We hope that the plugin developers will address this issue soon and provide a solution to this problem.

Recommendations

To resolve this issue, we recommend the following:

Update the plugin to recognize existing sets and themes when a user renames a collection or mode.
Provide a feature to update existing sets and themes when a user imports changes.
Test the plugin thoroughly to ensure that the issue is resolved.

Future Development

In the future, we recommend that the plugin developers focus on improving the plugin's functionality and user experience. This includes:

Enhancing the plugin's ability to recognize and update existing sets and themes.
Providing more features to improve user productivity and efficiency.
Improving the plugin's overall performance and stability.

Q: What is the issue with importing variable changes in the plugin?

A: The issue is that when a user renames a collection or mode and imports the changes, the plugin fails to update the existing sets and themes. Instead, it creates a new folder, set, and theme-group, forcing users to reapply tokens.

Q: What is the expected behavior of the plugin?

A: The expected behavior is that the plugin should update the existing sets and themes when a user renames a collection or mode. This would ensure that the changes are reflected correctly, and users don't have to reapply tokens.

Q: How can I reproduce the behavior?

A: To reproduce the behavior, follow these steps:

Import a collection and a mode into the plugin.
Rename the collection and mode in Figma.
Import the changes into the plugin.
See the error.

Q: What are the consequences of this issue?

A: The consequences of this issue are that users have to reapply tokens, which can be a tedious process, especially for large and complex designs. This can lead to frustration and decreased productivity.

Q: How can I report this issue to the plugin developers?

A: You can report this issue to the plugin developers by providing a detailed description of the issue, including steps to reproduce it, and any relevant screenshots or screencasts.

Q: What is the current status of the issue?

A: The current status of the issue is that it is a known bug, and the plugin developers are working to resolve it. However, no official fix has been released yet.

Q: How can I stay updated on the status of the issue?

A: You can stay updated on the status of the issue by following the plugin developers' social media channels or by checking the plugin's documentation for updates.

Q: What can I do in the meantime to work around the issue?

A: In the meantime, you can work around the issue by:

Creating a new folder, set, and theme-group for each change.
Reapplying tokens for each change.
Using a different plugin that does not have this issue.

Q: Will the plugin developers provide a fix for this issue?

A: Yes, the plugin developers have confirmed that they will provide a fix for this issue. However, no official release date has been announced yet.

Q: How can I contribute to the resolution of this issue?

A: You can contribute to the resolution of this issue by:

Reporting any additional issues or bugs related to this issue.
Providing feedback on the proposed fix.
Helping to test the fix once it is released.

By staying informed and engaged, you can help ensure that the plugin developers provide a fix for this issue and improve the overall user experience.