Add frontend validation to "Restrict membership by email domain" field
requested to merge 225543-add-frontend-validation-to-restrict-membership-by-email-field-in-group-settings-general into master
What does this MR do?
See #225543 (closed)
Adds frontend validation to the "Restrict membership by email domain" to improve UX. Error message is triggered when user hits the "Enter" key
Screenshots
Before
After
Local Testing
- Install a GitLab Silver License
- Create a new group
- Navigate to your group -> "Settings" -> "General" -> "Permissions, LFS, 2FA"
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry - [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
-
Separation of EE specific content
Availability 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 - [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
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
Edited by Peter Hegman