Enhancement based on GraphQL CRUD capabilities

[machi1990]

• Pagination https://graphqlcrud.org/docs/next/find#pagination
• CRUD operations see this https://graphqlcrud.org/docs/next/overview
• Filterings https://graphqlcrud.org/docs/next/find#filtering - Filter Implementation  #28
• Ordering https://graphqlcrud.org/docs/next/find#pagination
• Relationships, example in Graphback

/cc @ani-sha @rareddy

[machi1990]

I tested out the current master fa8438e, filtering seems to working (I'll perform extensive tests later on), but good job so far.

I have a question regarding the list query type e.g accounts from the shared image, are there plans to support pagination, i.e instead of returning the raw type but a container type that has raw type items and pagination info as indicated in https://graphqlcrud.org/docs/next/find#example-query

See:

/cc @rareddy @wtrocki @ani-sha

[ani-sha]

Yes, we have thought of adding pagination after modifying and implementing the filters entirely. There are a few more tests and functions to add.

[rareddy]

In the pagination scenario, what mechanism do you offer the user to get the "next" page after the first page is returned?

[wtrocki]

In dynamic systems using calculated cursor would be more appropriate.
We use limit and offset, but that is susceptible to seeing duplicates etc.

[wtrocki]

On the client side pages will be kept in the component state and deduplicated so we could provide support for two types of pagination:

• Unlimited scrolling (uses the client-side state to fetch the next page without calculating count)
• Client requests count and uses limit offset for classical pagination

While this has obvious challenges this is something we have implemented and we have flexibility to change offset to be used as generic string token to provide backward compatibility if we hit issues.

[rareddy]

ok, yes with offset you can see the potential for incorrect results when database state changed, but that is easiest otherwise we would need to build a local cache for it :(

How is paging done at the nested level? or this only at the top level?

[wtrocki]

Pagination and filtering can be done on the nested level as well by defining arguments to field directly for the type:

Example: