If you're just looking to implement a custom pagination solution there are a number of ways to go about it.

Simple Solution:
At a minimum you'd want to accept arguments to a field that track items such as startAt and pageSize to indicate to your server how many items you want (pageSize) and from which record you want to start retrieving from (startAt) and respond appropriately from your data source. You could even encapsulate that into an input object to make it a bit more standardized within your project and a custom output object to emit data in a standardized way for your clients. There are a lot of options that would depend on your specific scenario and what trade offs you want to work with.

public class UsersController : GraphController
{
   public IEnumerable<User> GetUsers(int startAt, int pageSize)
  {
      // retrieve users from your data source starting at the given record and 
      // returning the number indicating by pageSize
  }

}

Generalized Solution:
Taking it a step further to a more general purpose solution, such as an implementation of the specification, would require creating and registering a server extension to extend the library. An extension of this nature would touch almost every aspect of execution from type templating, schema validation rules, introspection data all the way to a field resolution middleware component to intercept and interpret a new set of internal objects. It would be a large undertaking.

Other examples of large extensions are the subscriptions library and file upload extension in the main library. Neither of these are similar enough to what would be necessary to build the connections extension but its a place to start if you want to learn more about implementing your own detailed custom extensions.

Hope this helps,
Kevin

[Q]: How to add pagination easilly #149

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions