strawberry_django_plus.filters.filter makes fields required by default?! about strawberry-django-plus HOT 3 OPEN

Hey @blueyed , are you sure that strawberry_django forthis should work just like strawberry_django forces the type annotation to optional?

I'll take a look over the weekend to check what is strawberry_django_plus doing differently

from strawberry-django-plus.

are you sure that strawberry_django forthis should work just like strawberry_django forces the type annotation to optional?

Can you please rephrase / fix your question? :)

I cannot really tell though: from my experience filters are optional/gql.UNSET by default, and while it appears to be a nice feature to require them, I do not think this should be the default behavior.

from strawberry-django-plus.

are you sure that strawberry_django forthis should work just like strawberry_django forces the type annotation to optional?

Can you please rephrase / fix your question? :)

OMG, I started typing something, than changed my mind in the middle and didn't reread what I wrote.

What I meant was to ask is: Are you sure strawberry_django works like that? Because the behaviour here should be the same AFAIK.

I cannot really tell though: from my experience filters are optional/gql.UNSET by default, and while it appears to be a nice feature to require them, I do not think this should be the default behavior.

I agree with you! It is just strange from the typing point of view. But well, if strawberry_django is already doing that (based on the question above), strawberry_django_plus shouldn't be working differently.

from strawberry-django-plus.