Use relatedKey instead of getKey in order to manage not-standard belongsTomany #73
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.
I've got this scenario.
Two models:
A
Rule
has a belongsToMany relationship withPersona
:This is the pivot table structure:
id, rule_id, persona_code
I would like to have in the pivot table not the Persona ->getKey but a custom key, in this case the
code
column: Laravel will allow me to do this using some extra parameter in belongsToMany.Without this PR, plugin will use
sync
method usingid
column and not the rightcode
column, inserting wrong data in database.I added a
$resource->{$parentModel->$relationship()->getRelatedKeyName()}
in order to get the right relatedKey.