View of data specific to the Authenticated User

[ptpaterson]

If you return a Page from a UDF, you should set pagination: true in @resolver.

If your UDF does not resolve into a Page, either because it’s a single object, or you Select('data',..., or otherwise return something not a Page, then the default is no pagination.

Be careful that your UDF specifies a large enough size so that it doesn’t drop any. default is 64. Max is 100000.

docs:

User-defined functions (for custom resolvers)

Some topics that might be helpful:

What is the Lambda signature for a graphql @resolver's UDF that both has 'pagination: true' and accepts arguments?

According to documentation here: I know that a resolver-UDF for a graphql query signature like this: pendingInvites: [Invite!] @resolver(paginated: true) Should have a signature like this: q.Lambda( ['size', 'after', 'before'], ... ) But what if the graphql query is expecting parameters? For instance, what would the signature for a UDF function be in the case of this graphql query: pendingInvites(active: Boolean!, user: ID!): [Invite!] @resolver(paginated: true) Now it needs…

Best Practices for custom GraphQL resolvers

More of a How-To, than a best practice, but since Pagination with GraphQL resolvers is a bit confusing, here are some things on that: Using Pagination Arguments in a UDF Docs can be helpful, even if they get a bad reputation! They have a good example of how to use pagination arguments in a UDF. I created a helper function that builds on that example: const paginateWithOptions = (set, size, after, before) => q.If( q.Equals(before, null), q.If( q.Equals(after, null), q.P…