ENT-11506: Handle duplicate enterprise group name validation error#2560
Merged
iloveagent57 merged 1 commit intoopenedx:masterfrom Mar 10, 2026
Merged
Conversation
8c4c727 to
cf8c032
Compare
rgopalrao-sonata-png
approved these changes
Mar 10, 2026
rgopalrao-sonata-png
left a comment
There was a problem hiding this comment.
Looks fine with all test cases
cf8c032 to
710c91c
Compare
test: add test cases for duplicate group error message test: add test cases for duplicate group error message fix: added test cases in serializers.py fix: added test cases in serializers.py chore: update changelog and version for duplicate group error fix
8fc1085 to
e54c27a
Compare
iloveagent57
approved these changes
Mar 10, 2026
This file contains hidden or 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.
Jira
https://2u-internal.atlassian.net/browse/ENT-11506
Description
Handled duplicate enterprise group name validation error returned from backend API.
Previously frontend displayed a generic "Something went wrong" message.
Now the API returns the proper validation error message which can be handled by frontend.
Changes