I've created 1000s of lines of server actions now, and on so many occasions I am copying a Set Value step because I want to assign the same variable a different value in a different situation... and each time I do that I need to go in and remove the '_copy' that gets appended to it.
Having variables with '_copy' on the end serves no useful purpose that I can think of. If I want a new name, I will give it one.
This is a request that copying a Set Value step causes the copied version to have the same name.
Although I would not mind _copy being removed on duplicating a server action step, it might lead to some issues as soon as you forget to change the name at some place, save the server action, run it and figure it out after 2 hours.
And post bug reports about values not properly returned as well as other errors in server actions.
Components names in server connect should not be same by default.
I can see completely why you’re frustrated. However, from a UX perspective if they were to remove the ‘_copy’ from a duplicated Set Value component then they would also need to remove this from all components, server and client side for consistency.
For entry level users this would be a major flaw. I can predict an increase in forum posts asking for help where they have duplicated a component, such as table, where instead of the id becoming table1, table 2 automatically, it is actually inserted as table, table, sharing the same id and causing a headache for newer less experienced users.
So so many times I copy a Set Value in a Server Action because I want to assign to the same variable in a different place and then have to remove this _copy text...
Not really a fan of this idea but perhaps a "duplicate extension string" setting within options defaulting to "_copy" but capable of being set to null.
