Missed globalMiddlewares option in BuildSchemaOptions for type-graphql

[manzonif]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

In type-graphql the globalMiddlewares option is available, which allows executing middleware on a global level, on queries and resolvers. However, it is not included in the BuildSchemaOptions interface of this module.

Expected behavior

export interface BuildSchemaOptions {
    dateScalarMode?: DateScalarMode;
    scalarsMap?: ScalarsTypeMap[];
   globalMiddlewares?: Array<Middleware<any>>
}

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Nest version: X.Y.Z

 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

[manzonif]

Sorry, now I know that type-graphql middlewares can't be used in Nestjs.

[jogelin]

@manzonif did you succeed to add a middleware for graphql ? I would like to be able to get back response from the full resolution of a query: @query + @ResolveConfig. With interceptors I can only get the result of the Query...

[manzonif]

@jogelin I solved my problem with NestInterceptor and GqlExecutionContext.
I am not aware of what @ResolveConfig is. Sorry.

[jogelin]

@jogelin I solved my problem with NestInterceptor and GqlExecutionContext.
I am not aware of what @ResolveConfig is. Sorry.

@manzonif Sorry I wanted to say @ResolveProperty()

It is related to #320 did you had this issue ?

[manzonif]

@jogelin my problem was related to this issue.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.