Global Guards are not triggered when route is registered with httpService.get('/route`) about nest

[lucassith]

Please ignore my dummy code, I get that registering routes this way:

  const server = app.getHttpAdapter();
  server.use('/test', (req, res) => {
    res.send(`test ${new Date().toISOString()}`);
  });

is wrong.

But please note that NestJS packges are using this way to register GraphQLModule in @nestjs/graphql and it allows everyone to query your entire database without any authorization, even though you have global guards registered.

https://github.com/nestjs/graphql/blob/c2e408f37c2842ba9c9df90bbd8cd80bd0cb3779/packages/apollo/lib/drivers/apollo-base.driver.ts#L139

[micalevisk]

to me, that's not wrong. It's a good way to slowly migrate an express/fastify app to nestjs, I guess

but yeah, not sure if that is a missing feature or a bug

[kamilmysliwiec]

This is the expected behavior. Any routes registered directly with the HttpServerAdapter are not wrapped with guards, interceptors, pipes, etc.