enforce unique key and team aliases in the ui #3572
Merged
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.
Title
Feature: enforce unique key and team aliases in the UI
Relevant issues
Fixes #3236
Type
🆕 New Feature
Changes
Testing
Manual testing:
Notes
this does not implement the uniqueness constraint on the backend, so calls to the API with the same key name could create keys or teams with duplicate aliases
OS Tests (optional but appreciated):