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
{{ message }}
This repository has been archived by the owner on Jul 16, 2021. It is now read-only.
Currently when using belongToMany it automatically uses the column that is set as the primary key on the models being used. This should not need to be set to change the columns used. I am proposing adding two new inputs to the method that will let you set the names of the columns for each of the tables.
The text was updated successfully, but these errors were encountered:
Can you please provide an example of what the proposed solution would look like for a developer coding it? Also elaborate on what use-cases within your application this would solve?
The proposed change would stop the assumption of belongToMany operators. So the belongToMany method would take in more variables that would have defaults and these changes would need to trickle down to any other method being called this way. I am not sure how deep this would go.
Currently when using belongToMany it automatically uses the column that is set as the primary key on the models being used. This should not need to be set to change the columns used. I am proposing adding two new inputs to the method that will let you set the names of the columns for each of the tables.
The text was updated successfully, but these errors were encountered: