Can't exclude user node fields "id" and "pk" about django-graphql-auth HOT 8 CLOSED

I'm not sure, but my first hunch is:

pk

Because it is a field in the UserNode, I didn't try, but probably trying to exclude archived/verified/secondary_email would result in the same warning

id

Because of graphene.relay.Node.Field that has an id field, resulting in the same case I wrote above for pk.

Being these cases, I don't plan to fix it, but I will investigate further to see if I find other possible reasons. If you make progress on this please let me know!

from django-graphql-auth.

What is the reason you chose for the relay interface for users?

from django-graphql-auth.

Because of the filtering. From the docs:

(...) filtering is automatically available when implementing a relay.Node. (...)

from django-graphql-auth.

It's odd, when I try to remove the id I don't get the warning message. When I try to remove the pk I get an exception:

Exception: "pk" exists on model <class 'users.models.CustomUser'> but it's not a field.

What version are you using of django-graphql-auth and graphene?

from django-graphql-auth.

It's odd, when I try to remove the id I don't get the warning message. When I try to remove the pk I get an exception:

Removing how?

Exception: "pk" exists on model <class 'users.models.CustomUser'> but it's not a field.

What version are you using of django-graphql-auth and graphene?

graphene==2.1.8
graphene-django==2.9.0
django-graphql-auth==0.3.8

from django-graphql-auth.

Removing how?

I mean, adding to USER_NODE_EXCLUDE_FIELDS .

from django-graphql-auth.

Shall I close this? Now that we have #27 coming up?

from django-graphql-auth.

yes, I close it

from django-graphql-auth.