You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fromModel is morphable, some of these model types may have an ancestors relationship that needs loading, some may not, this doesn't work due to not every morphable model having this relationship defined.
For morphable relationships any $with inclusions, as well as anything present in the include query, should conditionally include if the resolving model has that relationship available and defined.
The text was updated successfully, but these errors were encountered:
Thanks for raising. I think you're going to have to stick with the workaround for now, as the eager loading needs revamping to unlock several features on the development roadmap. I'll leave this issue open though as something to look into, either as part of that revamp or once the revamp has been done.
No problem @lindyhopchris - on reflection, this workaround doesn't as much feel like one. There would be limitations if you only wanted to do this contextually under one server, however not an issue right now.
Would be nice to have the same behaviour in the future on the Schema definition.
I have the following:
fromModel
is morphable, some of these model types may have anancestors
relationship that needs loading, some may not, this doesn't work due to not every morphable model having this relationship defined.For morphable relationships any $with inclusions, as well as anything present in the
include
query, should conditionally include if the resolving model has that relationship available and defined.The text was updated successfully, but these errors were encountered: