Open agmoss opened 2 years ago
Hey @agmoss,
Indeed, we do not handle graphQL for now but it could be nice to handle it. Unfortunately, I can't tell you when we can implement graphQL support.
I think we could create an option for graphQL, no need to create a new package. If you wish to, you can of course contribute and open a new PR to handle this 😁
Sounds great @ccoeurderoy! I will take a stab at a pr. Cheers
I converted two components, LoggingInterceptor and HttpExceptionFilter for GraphQL, including test code.
https://github.com/youngkiu/nestjs-graphql-components/tree/feat/graphql
Currently, the
LoggingInterceptor
does not work with graphql. Internal calls tointercept
,logNext
, andlogError
use the baseExecutionContext
from nest without first evaluating the current application context.Accessors for the in-flight request object are different depending on the application context. For rest they look like:
as you have in logNext
In graphql it looks like
(at least this is the cleanest way I have been able to access these)
As such, the use of rest style of access yields the following logs when in the graphql context:
Anyway, if you want to support gql with this interceptor I would be open to making a pr! Or perhaps I could add a new one that is specific for graphql.
This is a great assembly of nest utils!