Uniquify path slug creation from group name
requested to merge 32458-update-group-creation-url-so-it-is-always-unique-and-does-not-generate-an-error into master
What does this MR do?
Currently, if a user creates a group with a name that has already been taken they are hit with a large error. This is a disruptive experience to the user, if they update the group name, it does not update the URL which keeps the error active, the user must manually adjust the group URL to clear the error.
See issue #32458 (closed)
Note that backend already checks for namespace path slug uniqueness. This MR does frontend checks using the new suggests API.
- The very first group path suggestion is always unique by calling the
suggestsapi - If group path slug is already taken, give visual alert
Screenshots
| header | header | header |
|---|---|---|
 |
 |
 |
| The very first group path suggestion is always unique | If group path slug is already taken, give visual alert | If group path slug is available a text alert |
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation created/updated or follow-up review issue created -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Performance and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #32458 (closed)
Edited by Mike Greiling