Query does not support snake case query names about graphene HOT 4 CLOSED

Yes, that is the intended behavior. If you want the snake_cased name (which I don't recommend you do -- keep with convention and use camelCasing) you can simply pass name='work_order' to the Field constructor.

 class Query(ObjectType):
    work_order = Field(WorkOrder, id=graphene.Argument(graphene.String), name='work_order')

    @resolve_only_args
    def resolve_work_order(self, id):
        return WorkOrder(id='1', state='test')

from graphene.

Great, thanks. I am more concerned with the fields when defining the schema actually, where name seems to work as well:

class WorkOrder(Node):
    id = IDField()
    state = StringField()
    nodes = ListField(WorkOrderNode)
    req_uid = StringField(name='req_uid')

Since we are defining the schema in python it is nice to make it more pythonic. Why don't you recommend using snake case?

from graphene.

The schema is generally going to be consumed by a JavaScript application. Casing there is camel. Graphene will keep things in Python snake cased, but outwards facing graphQl schema will be camel cased which is generally the convention for JavaScript and grqphQL.

from graphene.

Thanks for the clarification!

from graphene.