[7.x] Fix augmentation on frontend routes #610
Merged
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
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.
This pull request fixes an issue where fields weren't being augmented correctly on frontend routes.
This issue was caused by #590, where we started passing the model to
->cascadeContent()instead of passing the augmented array to->with().However, this meant that the data on frontend routes wasn't being augmented since
Cascade::hydrateContent()checks if the data (the Eloquent Model in this case) implements theAugmentableinterface which models aren't implementing.Since there's no way for us to add the interface in Runway's traits, we're just passing the augmented data along again to
->with()which fixes the issue.Fixes #606.