Allow Deleted Owners and Entities to be Resolved and Fix LazyLoadingViolation When Loading Owners
#57
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.
Deleted Models: When records are soft deleted, the
morphTorelationships returnnull. This allows records that have been soft deleted to still be returned.logger:audit-resolvercommand. Now, theentityrelationship can be loaded even if the Entity has been deleted.ownerrelationship isn't loaded as part of the command, addingwithTrashedto it will allow the owner to be loaded when dealing with the audit record directly.LazyLoadingViolationError: This error may occur when callingtrackableOwnerResolveron an entity and the resulting owner model was already previously loaded (2+ entities are referring to the same owner in type and ID, see rows with IDs 3-8 below)To fix this, every tracked model must define a
getOwnerRelationshipNamefunction that returns the name of the owner relationship to be loaded, ornullif a tracked model/entity is also its owner. The return value of this function is used to load the owner relationships when thelogger:audit-resolvercommand is ran.