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
Is it on purpose that one is not able to resolve a user from a custom Django model (called 'Component' in my case) that is related to a user via a ForeignKey? When I try to query the user field (called 'creator' in my case) I receive the following error message: "Cannot query field "creator" on type "ComponentNode""
The issue originates from the usage of the seemingly undocumented Meta property 'skip_registry' of graphenes 'DjangoObjectType' in the definition of the UserNode class. What is the reason and purpose for setting 'skip_registry' to True?
Expected behavior
Access non-critical user properties (like username and id) from related objects
Actual behavior
The relation between a custom Django model and a user is not resolved from a graphql query to the custom model
The text was updated successfully, but these errors were encountered:
Prerequisites
For more information, see the CONTRIBUTING guide.
Description
Is it on purpose that one is not able to resolve a user from a custom Django model (called 'Component' in my case) that is related to a user via a ForeignKey? When I try to query the user field (called 'creator' in my case) I receive the following error message: "Cannot query field "creator" on type "ComponentNode""
The issue originates from the usage of the seemingly undocumented Meta property 'skip_registry' of graphenes 'DjangoObjectType' in the definition of the UserNode class.
What is the reason and purpose for setting 'skip_registry' to True?
Expected behavior
Access non-critical user properties (like username and id) from related objects
Actual behavior
The relation between a custom Django model and a user is not resolved from a graphql query to the custom model
The text was updated successfully, but these errors were encountered: