-
Notifications
You must be signed in to change notification settings - Fork 2
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
Handle renaming conflicts #195
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is nice but the feature missing is to be able to overwrite existing presets and set presets. you used to be able to do that via specifying the same name when saving but it would be nicer to just do that via the action menu like we do we sets.
0fc9807
to
0ea5d8c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great, final thing is i think we should probably trim the name the user types in.
i can save "foo" and then "foo "
…niquename generation
… code and ensured that the confirm dialogue is always shown upon overwrite
28ab953
to
f766045
Compare
ok I rebased on |
This PR prevents overwriting existing presets (both on instance as well as set level), sets and setviews by ensuring name conflicts are marked as an error.
Note I made this PR on top of the views work to get uniqueness validation for SetViews in there already as well as resusing the
getUniqueName
util that was already in place here.closes #147