feat: support graphql in request interceptor

[MiffyLiye]

Description

• Support GraphQL in request interceptor
• When request is not RESTful or GraphQL, do nothing in request interceptor

Issue ticket number and link

https://github.com/Wiredcraft/nestjs-boilerplate/issues/192

[jiangmengyu0409]

I was having a question on what is the best place to define and import the GraplqlModule? I was defining it in the CommonModule like what we do for CouchbaseModule, and then import this Module in the other modules that need it. Should we do the same here instead of directly define its initialization on the AppModule?

[MiffyLiye]

we can move the discussion to the original issue https://github.com/Wiredcraft/nestjs-boilerplate/issues/192
as a test setup, I prefer to keep it slim: register graphql module, controller and resolver in app module.

[xavierchow]

context.getType() repeats multiple times, is it better to separate the extracting req/res from the context into another place so that intercept only takes care higher level logging tasks.

[MiffyLiye]

moved extracting req / res in a function in a new commit.

[xavierchow]

Support GraphQL in request interceptor

I'm not quite familiar with GraphQL, do we have an alignment about what to log for a GraphQL request?
Most information is in the payload(request / response body), but it will be too verbose to record the whole body, no? @MiffyLiye

[MiffyLiye]

do we have an alignment about what to log for a GraphQL request?
Most information is in the payload(request / response body), but it will be too verbose to record the whole body, no?

Currently logs same fields as restful request,
the request / response body converts to short-body with max length 100,
whether log full details of the query will need alignment.

[xavierchow]

hold on until we have some progress about https://github.com/Wiredcraft/nestjs-boilerplate/issues/192#issuecomment-1523184902.

[xavierchow]

the logging format of graphql request body can be optimized with other PRs.

[MiffyLiye]

in short term, use excludeReqPath to skip graphql requests in interceptor, and add logger in each graphql resolver class.
in long term, a graphql apollo server plugin should be added to log graphql request / response.