[4.x] Prevent calling notifications
method on User
model
#9936
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 when storing users in a database, where if you have a column called
notifications
, an error would be thrown during augmentation.This was happening due to the Eloquent
User
model having anotifications
method which returns amorphMany
relationship, which our augmentation stuff doesn't know how to work with.This PR fixes that by preventing the method on the
User
being called and falls back to checking the raw data on the user instead.Fixes #9932.