Enforce unique names ADO 2223 #64
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes did you make?
Enforced uniqueness of names for Fields, Groups, and Select Options (at the front-end level). Also made name, label, and (in the case of Select Options) values searchable in the view table, which will help identify any existing duplicated names
Why did you make these changes?
Implementing https://dev.azure.com/BC-SDPR/Forms%20Modernization/_workitems/edit/2223
What alternatives did you consider?
Considered adding validation to the database, but frontend is sufficient and avoids any potential errors with any existing duplicates, which can be safely caught fixed manually
Checklist