Accessing context in custom decorators.

[jbeckton]

Not sure what I am doing wrong here but whenever I reference context in my decorator then the graphql query request hangs and never completes.

Here is how I am setting up apollo.

 app.use(
    '/graphql',
    cors<cors.CorsRequest>(),
    express.json(),
    expressMiddleware(server as ApolloServer<MyContext>, {
      context: async ({ req }) => ({
        req,
        token: req.headers?.token as string | undefined,
        prisma,
      }),
    }),
  );
 

Here is how I build my schema.

const resolversEnhanceMap: ResolversEnhanceMap = {
    Post: {
      _query: [HasAbility('throw')],
    },
  };

  applyResolversEnhanceMap(resolversEnhanceMap);

  const schema = await tq.buildSchema({
    validate: false, // Enable 'class-validator' integration..
    resolvers,
    // Register 3rd party IOC container
    container: Container,
    // Create 'schema.graphql' file with schema definition in current directory
    emitSchemaFile: path.resolve(__dirname, 'schema.graphql'),
  });

here is my decorator function.

export function HasAbility(input: string) {
  return createMethodDecorator(async ({ args, context, info }: any, next) => {
    console.log('HasAbility input %o', input);
    console.log('HasAbility context %o', context); // <-- this causes the request to hang 

    return next();
  });

[MichalLytek]

Hard to tell without a minimal reproducible code example repository.

[carlocorradini]

@jbeckton Yes!
Mostly every example is based on Apollo Server v4 (https://github.com/MichalLytek/type-graphql/blob/master/examples%2Fsimple-usage%2Findex.ts)

[jbeckton]

I am also using typegraphql-prisma v0.27.2, looking at the examples from that repo they are using ApolloServer v3.

https://github.com/MichalLytek/typegraphql-prisma/blob/main/examples/1-prototyping/package.json
https://github.com/MichalLytek/typegraphql-prisma/blob/main/examples/2-basic/package.json

Could this be causing the issue?

I guess this lib just isn't for me, I have been trying for a couple days now to figure out why referencing context inside middleware or a decorator function causes the request to hang. Using code snippets from your own docs and referred to the apollo server docs a bit as well. I'm not trying to get creative but just get some simple examples running on my own models. I was hoping to avoid having to hand code all the boilerplate to get a crud api working but given the tradeoffs of my labor vs quirky unpredictable third party code I guess I better get busy building that boilerplate.

[jbeckton]

Apollo Server v4 requires an async function for loading context, v3 does not. Maybe the code that typegraphql-prisma generates does not utilize the async function for context? The behavior I am experiencing is just like what I would expect if a promise does not get resolved, the process will just sit there and wait for it to resolve but it never does.

[jbeckton]

I guess I don't understand why...

authChecker.ts

// OK
console.log('TOKEN', context['token']);

// OK
console.log('FINDMANY', context['prisma'].post.findMany());

// Crashes app
console.log('context', context);

[MichalLytek]

Oh, if you try to console log the whole context object that might contain prisma instance, it's very heavy to serialize for some reason. So just do not log whole context with prisma 😛 It's not TypeGraphQL issue.

[jbeckton]

I discovered a work around for this issue. Thanks for your help.