Fix the way join keys are set for a relation that's instance of HasManyThrough #22
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.
A user can specify a different
secondLocalKey
.The current implementation is always looking for the
getQualifiedKeyName
of the parent which assumes is the value returned bygetKeyName
In this new version, it's going to look at the
$relation->getQualifiedParentKeyName()
which is retrieved based on the value that was set forsecondLocalKey
when the relation was defined.