update can only target a single resource #1648
Merged
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
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.
An update can only target a single resource. Speaking of "targeted resource(s)" may confuse the reader therefore.
An update may affect multiple resources if it has side-effects. E.g. updating a
ratingresource may indirectly updateaverageRatingattribute of a relatedproductresource. But nevertheless the update only targets theratingresource.The difference between targeted and affected resources is important. HTTP response status codes required by the specification only depends on targeted resources. E.g. a server must include the targeted resource in response if it has been changed in any other way than specified. But a server may or may not include another, non-targeted resource in response even if it has been changed due to a side-effect.
A similar issue for "targeted relationship(s)" has been fixed in #1638 (comment).