Provide additional information to shouldIncludeLinkageData() #550
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
- add `descendant` flag when calling `shouldIncludeLinkageData` to provide information with regards to the depth of serialization being requested
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.
Some server implementations will not serialize all included relationships because this would make for a very large payload.
This PR provides a fix for #548 by adding an isIncludedResource flag when calling shouldIncludeLinkageData. This allows the developer of a mirage implementation to know whether or not an included resource is being requested and can therefore make a decision as to whether or not to serialize that as well.