Is it possible to use the NexusContext in a utility method outside of a resolver?

[uncvrd]

Hey! Quick question...I defined a helper method to request an access token from my database, then check if it is valid and return the existing token or create/return a new one. I extracted this because I have to retrieve this token several times in different resolvers. My question is, is it possible to access the NexusContext within this utility method without having to pass the ctx from the resolver in to the method?

From my understanding, I can extract the PrismaClient from nexus-plugin-prisma/client and create a new instance, however, this obviously isn't typed with my database models.

Use case:

In graphql resolver:

resolve(_root, _args, ctx) {
  // i need to request the ctx in my getToken method, so I need to pass ctx here
  const token = getToken(ctx);
  .....
},

In util method:

const getToken = (ctx: NexusContext) {
    // might be nice to do let context = new PrismaClient()? 
    const token = ctx.db.token.findOne({...})
    .....
    return token
}

[ChloeWard12]

I'd keep passing ctx into the helper. It's a common pattern in GraphQL because the context is request-scoped and may contain more than just the Prisma client, like auth data, loaders, or request metadata. Creating a new Prisma client inside the utility isn't ideal since it can lead to extra connections and bypass your existing context setup. If you only need the database, another option is to pass ctx.db instead of the entire context to keep the helper simpler and easier to test. 7Bit Casino offers a wide https://7bit.casinologin.mobi/ selection of slots, table games, and crypto-friendly payment options.