Fix - getRelated()
on null for relationship discovery
#790
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.
Namaskar,
This PR addresses an issue by introducing an additional
instanceof
check for the$relation
to see if it's a valid relationship, in the EloquentEntitySet driver. If not, bail early.lodata/src/Drivers/EloquentEntitySet.php
Line 517 in 1c3b45a
I'm not sure as to why even in case of a null exception, the
get_class
is not bailing, but doing a check to bail seems to work.Here's a stack trace where I was able to encounter this issue: https://flareapp.io/share/J7oxAYx5
Here's the offending model snippet, the
...
denotes parts that have nothing to do with the bug:OdataCompanies
Class:Essentially loaded into as a provider.
Additional information:
Note it's essentially the stock Laravel 10.x sail docker image.