Resolves #263 added a means to disable attaching relationship metadata on unresolved includes #264
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
…p metadata on unresolved includes
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.
Screenshot
N/A
What Changed & Why
Learn more at #263
Introduced a flag
attachRelationshipDataOnUnresolvedIncludeswhich by default is set to true for backwards-compatibility purposes.When set to true, Devour will continue to attach relationship metadata in the client's response on unresolved includes as it normally does.
When set to false however, Devour will abstain from attaching such metatada. This applies both for relationships of type
hasManyandhasOne-Testing
Just run the tests.
Documentation
Updated the README file with instructions.