Check if a relation actually exists in a table column, otherwise assume an array should be accessed #3378
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.
Post model
Currently, line A throws a RelationNotFoundException because
queriesRelationship()
does not check if the relation actually exists. With the new behaviour, a check is being done before assuming a relation exists.HasLabel
, but displaying the last part as label make more sense.$this->getRecord()
can returnnull
, when it does it will be assumed no relation exists. Is that the correct behaviour?