graphene
graphene copied to clipboard
GraphQL framework for Python
When resolving a query with duplicated nested fields with different selection sets, only the first selection set is available to the resolver info AST. Given the following query: ```gql query...
## Context I'm currently trying to set my model user `User` subfield `user.actor.id` as field source of my `DjangoObjectType`. This happens because there's other kind of users within the application...
resolves #1296
Is there a feature already existing for dataLoaders to load graphene RESTFUL APIs as datasource current Behaviour https://docs.graphene-python.org/en/latest/execution/dataloader/#using-with-graphene Existing docs provide info to load the data from database and load...
There is the `BigInt` type https://github.com/graphql-python/graphene/blob/72c2fd5ec38af595519b2ab334696397760d2d81/graphene/types/scalars.py#L85 but it's not exposed here https://github.com/graphql-python/graphene/blob/72c2fd5ec38af595519b2ab334696397760d2d81/graphene/__init__.py#L11
Adds some documentation and examples to help those struggling with the type resolution of Unions (like I myself was just recently). As this is my first real contribution to this...
Hi folks, I'm raising this issue to gauge ideas from the Python community on error handling best practices. The usual way to handle errors in GraphQL is by inspecting the...
Graphene offers a convenient method to convert a Python-Enum (`PyEnum`) to a graphene-compatible enum (`GEnum`) using the `types.Enum.from_enum()` function. However, this function creates a new type each time it is...
In `InputObjectType.__init_subclass_with_meta__`, the `fields` of the `Meta` class (passed as an `options` arg) are never referenced. This in effect just skips them completely wich stands in contradiction to the docstring....
``` .venv/lib/python3.8/site-packages/graphene/utils/subclass_with_meta.py:46 /app/.venv/lib/python3.8/site-packages/graphene/utils/subclass_with_meta.py:46: DeprecationWarning: Creating a DjangoObjectType without either the `fields` or the `exclude` option is deprecated. Add an explicit `fields = '__all__'` option on DjangoObjectType NAMI to use all...