Prevent/recover from accidentally overwriting a loadout

[Revadike]

Proposed change

Replace button "save as new" loadout with a toggle instead

How does this fit into your workflow?

Too often I meant to duplicate/copy a build (when making a variant), but I end up replacing it instead by accident, with no way to recover....

[bhollis]

It's definitely frustrating if that happens, and it sucks that you can't currently recover from it. I don't think the solution is a toggle, and we don't want to add overwrite confirmation since it's such a common workflow. Here are some other thoughts:

1. You could change your workflow to always start out saving as new to make a copy, then editing the copy. That way you won't make a mistake later after you've customized the loadout.

2. We could allow undoing an overwrite of a loadout, either from a notification or something else. This would pair well with the task to add a Notification Center.

[Revadike]

1. I usually do this, but it's quite cumbersome and sometimes I forget
2. Version history could also work, but it'd increase the storage amount

[nev-r]

definitely have exact same problem sometimes. and it's a bummer when it happens. a button to [copy loadout and immediately edit the copy] could be cool

[Revadike]

yeah something like that

[chehitskenniexd]

would love to take a crack at this is y'all don't mind!

some questions:

1. assuming a copy and edit button is added, where would be most appropriate to add it? e.g. would it go in the loadout popup below or would it go in the button cluster on a loadoutrow as shown below?

2. is/are there any testing framework(s) setup (e.g. cypress) to test FE interactions?