I have a custom input object type

class Filters(graphene.InputObjectType):                                        
    name = graphene.String()
    type = graphene.List(graphene.String)

and the query definition

class Query(graphene.ObjectType):                                               
    search = graphene.Field(
        SearchResult, query=graphene.String(require

Hey! When I was reading the docs and I saw api.background.task, the first thing that popped into my head was "but you can just use asyncio.create_task or loop,.run_in_executor for that without inventing something new!". But then I noticed that it also passes the context vars to the synchronous backround stuff, which is nice. Wonder why that's not the case in the stdlib, cause it would be nic

strawberry.utils.typing.get_optional_annotation fails when provided an Optional[Union]

>>> from typing import Optional, Union
>>> from strawberry.utils.typing import get_optional_annotation

>>> get_optional_annotation(Optional[Union[int, str]])
<class 'int'>

This should return Union[int, str] instead

Modify the setup.py so it produce bdist_wheel for manylinux including the libgraphqlparser.so/a
Modify the build process so this wheel is uploaded to pypi
Modify the cffi part of tartiflette/parser so it loads this lib instead of the local one.

Make a concise print function for the QueryPlanningAnalysis class https://github.com/kensho-technologies/graphql-compiler/blob/v2.0.0.dev25/graphql_compiler/cost_estimation/analysis.py#L381

In most cases, the printout of the analysis passes is enough to explain why a particular query plan was chosen.

Loving this project.

I feel like this project would benefit from a short quick start tutorial that demonstrate common methods such as:

Create item

    mutation = Operation(schema.Mutation)  # note 'schema.'
    mutation.create_item(input=dict(id="23432")).__fields__()

List items with filter

    op = Operation(schema.Query)  # note 'schema.'
    op.list_it

Hi

I have been using graphene-mongo for a while now. I use all resolvers and mutations post validation of an Access token in the HTTP Authorization header. However, I am not aware of how I can do that for a MongoengineCollectionField

For example, I have defined it as follows

class Query(graphene.ObjectType):
    all_projects_to_models = MongoengineConnectionField(Project)