Idea: expose more details on pagination

[eamigo86]

Idea: expose more details on pagination

[eamigo86]

Hi @basilfx, I will work to make the configuration of the page more friendly, in the next days I will update the module with the changes and I will let you know.
Thanks for the suggestions that will always be welcome. regards

[basilfx]

Tested the new option, and it works like a charm. I did not use the settings in settings.py, but just in the constructor itself.

[eamigo86]

Hi @basilfx, I have uploaded a new version (0.0.1rc2) with the possibility of choosing the pagination type and the number of elements of each page in a global way in the settings.py, I still have to update the documentation (I'm lazy doing it), but in essence it can be configured like this:

GRAPHENE_DJANGO_EXTRAS = {
    # Default Pagination: None
    'DEFAULT_PAGINATION_CLASS': "graphene_django_extras.pagination.LimitOffsetGraphqlPagination",

    # Default: None
    'PAGE_SIZE':  100,
}

Regardless of pagination type, you will see in the parameter description the values of the default limits and the maximum limit of the each page size, example (LimitOffsetGraphqlPagination):

These parameters can be configured by specifying the pagination in each DjangoObjectListType:

In this case (LimitOffsetGraphqlPagination), if the max_limit value is not specified when defining the pagination type in the DjangoObjectListType definition, the request can be made without limit size, but if a max_limit or a default_limit is not specified and a PAGE_SIZE is not specified in setting.py, the query will return None, just as it happens in the DjangoRestFramework module.

Similarly if you try to set a limit that is greater than the defined max_limit or not specify at all, the size of the paginate will be the value of max_limit specified in DjangoObjectListType definition (in this case: max 6 users):

A similar configuration works with PageGraphqlPagination, but instead of max_limit and default_limit, you should use: page_size and max_page_size.

It is difficult to return the actual limit (page size) that is used to the request as you suggested, I will continue to look for an optimal way to give that possibility, for now this is everything.