chore(docs): added example for m2m through fields
#116
Conversation
|
Looks like flake8 has moved repo and the config needs to be updated: |
| Using `graphene-django-cud`, a `through` model is more akin to a many to one relationship, as it is | ||
| an intermediate model that connects two other models with itself. |
There was a problem hiding this comment.
I think we should rewrite this to specify that this is how Django handles through fields internally (via a ManyToOneRel, although we don't need to specify that). This leads to many_to_one_extras being a more viable option to use with through intermediary models.
It is not something we enforce, it is something Django itself enforces.
| There's also usually no need to specify the `many_to_many_extras` field, as | ||
| the `through` model will be used instead. |
There was a problem hiding this comment.
Maybe expand on this to note that the m2m-field will be autogenerated with the input schema, but that it is less useful when using a through-model—and that excluding it might be a good idea.
We should also probably consider auto-excluding the m2m-variants from the schema when encountering a m2m-relation with a through.
|
Closing due to inactivity. Feel free to continue on the branch and file a new PR when the comments are adressed. |
No description provided.