ModelCreateMutation generates required fields for CharFields without null=True. about graphene-django-plus HOT 4 CLOSED

Although a pretty simple workaround is to define the required_fields meta option.

from graphene-django-plus.

Hi @gghildyal

Hrm, I see what you mean. Yes, I agree with you. Most of the code is based on graphene's fields generation from django models and it mapps null to required (because most of the code is used for output).

Maybe we should force the required to consider blank? My only concern would be breaking the api too much =P. But maybe it is for the better!

from graphene-django-plus.

Hi @bellini666

You are right about the fact that its graphene's field generation that causes null fields to come up as required, so its an issue with this library per se. And given that theres is an easy workaround to it, I don't think it's a big issue.

from graphene-django-plus.

@gghildyal was thinking about this issue and I think it is correct to consider the blank for requireness. Am going to do a change about this today.

from graphene-django-plus.