Where does ctx.users.resolveForConnection() come from when defining a t.connection() in the docs?

[uncvrd]

I'm looking in to relay style pagination and I see that Nexus has a t.connection() field. I noticed that the nodes example resolves by using a ctx.users.resolveForConnection(root, args, ctx, info). Where is this resolveForConnection() method defined and what does it look like? Is this just an extension off of a findMany?

Link to the docs I'm referencing: https://nexusjs.org/api/nexus/schema#tconnection at the very bottom it has this exmaple:

schema.queryType({
  definition(t) {
    t.connection('users', {
      type: 'User',
      nodes(root, args, ctx, info) {
        // [{ id: 1,  ... }, ..., { id: 10, ... }]
       // where is this defined and what is it's structure?
        return ctx.users.resolveForConnection(root, args, ctx, info)
      },
    })
  },
})

Thanks!

EDIT: ok so from what it looks like, I need to make use of schema.addToContext() and define a method called resolveForConnection()? Why not just use the ctx passed from the nodes() to run a findMany() query here?

[Weakky]

Hey @uncvrd, you don't have to specifically use a method called resolveForConnection. This is purely just an example. You're free to use whatever method you like as long as it fulfills the requirements of the type User you're pointing to 👍

[uncvrd]

@Weakky ok got it! For some reason I thought it was a method I was missing 😅 still new to relay style pagination. Thanks!

[mohe2015]

I was also irritated by that so maybe change it? Like "yourCustomResolveForConnection" or something like that. Or just note that you need to implement that by yourself?