set_related: allow custom types with set_reversed=False#333
Merged
Conversation
Member
|
Test breakages on 3.7 and 3.8 does not seem to be related to this patch |
Member
|
Thanks for the contribution. We should also consider RFC 9253 also and extend |
Contributor
Author
|
Thanks for the fast answer & merge |
Member
|
@Zocker1999NET, do you by any chance have the time to comment on my related work in #336 ? |
20 tasks
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
2 participants
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.
Method failed before when using a custom relation type. Specification explicitly allows custom X-Types for non-standardized use cases. This also makes the library future-proof if futher relation types are added.
Also extract RELTYPE_REVERSER constant from method for good practice.
Tested for my use case (using a custom type) locally.