-
Notifications
You must be signed in to change notification settings - Fork 299
Make HyperlinkedRelatedField includable #733
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
4c23d01
to
7165a8b
Compare
7165a8b
to
9c0819d
Compare
Codecov Report
@@ Coverage Diff @@ ## master #733 +/- ## ========================================== - Coverage 97.08% 97.04% -0.04% ========================================== Files 54 54 Lines 2742 2744 +2 ========================================== + Hits 2662 2663 +1 - Misses 80 81 +1
Continue to review full report at Codecov.
|
@sliverc would you mind taking a look at this PR ?
Not so sure this is a good idea. A relationship doesn't need to have a relationship pointing back to its parent and therefore we will have an included resource object which is not linked in the compound document.
Also see specification in terms of full linkage. What in the specification do you think would allow combining includes and links in a way this PR allows it?
Any feedback to #733 (comment) or shall we close this PR?
@sliverc Yep, the comment makes a sense and looks like we cannot include related objects if there are no links from resource object due to the spec. I think it can be closed
For now it is impossible to skip "data" rendering for any relation and be able to
include
it via GET parameter. This PR fixes thatDescription of the Change
It fails to GET api/product/1/?include=variants
But with this PR it will work
Checklist
CHANGELOG.md
updated (only for user relevant changes)AUTHORS