Graphene: Document how to implement Connection fields and pagination

[antoine-gallix]

From the documentation on relay Connection, there is an example on how to define a connection object type, but in the part that shows how to define a connection field, it's not clear what should the resolver return. The example only show an empty list returned. What type of object is a connection resolver supposed to return? Could you show a concrete example?

Also the sentence in that paragraph is not clear:

You can create connection fields in any Connection, in case any ObjectType that implements Node will have a default Connection.

What does this sentence mean?

[antoine-gallix]

What I found out:

The following worked to define a List field

class Thing(SQLAlchemyObjectType):
    class Meta:
        model = models.Thing # sqlalchemy model

things = graphene.List(ThingGraphQLType)

@staticmethod
def resolve_things(args, info):
    # returning a query seems to be ok
    return Thing.get_query(info=info)

However the following does not:

class ThingConnection(relay.Connection):
    class Meta:
        node = Thing

things = relay.ConnectionField(ThingConnection)

@staticmethod
def resolve_things(args, info):
    return Thing.get_query(info=info)

graphql.error.located_error.GraphQLLocatedError: object of type 'BaseQuery' has no len()

But this works:

@staticmethod
def resolve_things(args, info):
    return Thing.get_query(info=info).all()

This is all based on try and error. That could be nice to explain that upfront in the doc.

[antoine-gallix]

After the previous declaration, I see on my schema that ThingConnection exposes first,last,before and after. This makes me think that pagination is implemented.

However if I try to use the first argument in my query, like things(first:1) {edges{node{name}}}, I get back an error like graphql.error.located_error.GraphQLLocatedError: resolve_farm_connection() got an unexpected keyword argument 'first'

Looks like it's not implemented. So I add the first argument to my resolver signature, without actually implementing the pagination:

@staticmethod
resolve_things(args,info,first=None):
    # 'first' argument is not used anywhere, only added to the signature
    return models.Things.query().all()

There is three Things in my db. If I query things {edges{node{name}}}, I get 3 edges. Then if things(first:1) {edges{node{name}}}, I get only one. So after all even if I don't implement it myself, something in the Connection class will do it. But I still need to allow first in the resolver signature.

I keep exploring this package but it's a slow process of try and error to discover features, find out what is possible and how to do it. The documentation is really lacking in this area.

[louisdvs]

Agree that it's a huge trial and error effort to understand this lib. My understanding is that pagination is implemented on the edges, you appear to be trying to implement it on the root node. ie I think:
things(first:1) {edges{node{name}}}
should be:
things{edges(first:1){node{name}}}
This keeps it clean when you want to filter things, then paginate the results ie:

things(name:$name,type:$type)
      { edges(first:$limit) {
         node{
           name
         }
       }
    }

That is the benefit that you get from having the tedious amount of boilerplate in your queries.

[antoine-gallix]

Ok I'll start completing the doc as I discover about the package: https://github.com/graphql-python/graphene/pull/892

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.