Feat/#151: Many-to-Many Support via [HasManyThrough] #419
Conversation
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
Merged
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.
Closes #151
FEATURE
NOTES
[Q] When PATCH-ing a HasManyThrough relationship, what happens if the through type has other properties besides the navigation properties?
[A] This operation acts as a PUT operation. It will remove any old join entities and create new ones. So, any attributes on the join entity will be set to
default(T). This is because we don't have a good way to communicate the concept of updating a specific member of a HasMany set. If you need to update the join entity attributes, that should be done using normal json:api resources. I would also recommend considering json:api v1.1 operations for this use case.