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
With DjangoFilterConnectionField, neither edges or nodes will ever be null. These being nullable gives extra work when using the schema, since we will have to unnecessarily check for null a lot.
It might be an idea to make the JoblistingConnection itselt nonnullable as well, since this is only null in the event that we also get an error. (i.e. illegal arguments).
With
DjangoFilterConnectionField
, neither edges or nodes will ever benull
. These being nullable gives extra work when using the schema, since we will have to unnecessarily check for null a lot.Currently, our schema looks like this:
What we want:
It might be an idea to make the
JoblistingConnection
itselt nonnullable as well, since this is only null in the event that we also get an error. (i.e. illegal arguments).See also: graphql-python/graphene-django#901
The text was updated successfully, but these errors were encountered: