You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the user can edit a palette's name to one that's already in use by another palette. This is undesired behaviour, since we use the palettes names' as keys on local storage. If the user tries to rename a palette to a name that's already in use, the app should show a red toast message saying "{{ name }} is already in use" or something like it, and cancel the operation.
Leaving a palette's name empty shouldn't be allowed either.
The text was updated successfully, but these errors were encountered:
Currently, the user can edit a palette's name to one that's already in use by another palette. This is undesired behaviour, since we use the palettes names' as keys on local storage. If the user tries to rename a palette to a name that's already in use, the app should show a red toast message saying "{{ name }} is already in use" or something like it, and cancel the operation.
Leaving a palette's name empty shouldn't be allowed either.
The text was updated successfully, but these errors were encountered: