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
{{ message }}
This repository has been archived by the owner on Feb 16, 2024. It is now read-only.
It's easy for two admins to decide to add a person, and then we have duplicate entries. There is no enforced uniqueness check on the fullname field in case there really are two people with the same name.
Proposed solution
When saving a new person, have the UI check for fullname uniqueness and show a modal warning that lets the admin know about the possible collision. They can either go ahead and save anyway, or go back to editing the unsaved entry.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It's easy for two admins to decide to add a person, and then we have duplicate entries. There is no enforced uniqueness check on the
fullname
field in case there really are two people with the same name.Proposed solution
When saving a new person, have the UI check for fullname uniqueness and show a modal warning that lets the admin know about the possible collision. They can either go ahead and save anyway, or go back to editing the unsaved entry.
The text was updated successfully, but these errors were encountered: