Renaming component's default state
Components can be very different from one another and the initial state can mean different contexts to the user.
Let us be able to rename the component's default state, so it can make more sense during the component building process.
-
Iryna Shcharbakova commented
+ Replacing the default state by any other state, please - it helps to organize the library
-
بيان ماجد commented
we also need to be able to replace the default state by one of the states or to be able to delete it
-
Laura commented
a double click on the master component 'default state' to activate a renaming in same way you can rename states would be very helpful for file organisation - especially working with large libraries.
-
Christine commented
This would be a wonderful change. When working with Flutter developers, 'default' is keyword in dart and is causing confusion when I pass off my files to my development team.
-
David Holden commented
replacing the default state with another state (changing order) would also be useful
-
Tony Riley commented
I would like to be able to rename Component states too, please.
-
Duc Dao commented
Yess
-
Alkisti commented
I agree, it would be very useful.
-
Robert Boyhan commented
YES! For example, you might have a set of badges with different styling on each one: Approved, Pending, Draft, etc. None of those is the "Default" state. And if you can't rename it, you have to try to remember which of those styles you made as the default state.
-
Anonymous commented
yesssss please