14033 raise validation error if A and B term go to same object #14050
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
abhi1693
reviewed
Oct 16, 2023
jeremystretch
requested changes
Oct 17, 2023
There was a problem hiding this comment.
Per @abhi1693's comment, let's move this logic from the form to Cable.clean() to ensure the same validation is applied for cables created via the REST API as well.
jeremystretch
approved these changes
Nov 1, 2023
|
Thanks @arthanson! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes: #14033
On cable creation, don't allow cables to have A and B terminations pointing to the same object.