Exception filters with GraphQL

I’m submitting a…

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

Current behavior

I follow this documentation https://docs.nestjs.com/exception-filters for apply a filter for exception in a graphql resolver, over a mutation function. But the exception is never catch.

Expected behavior

Catch the exception in graphql resolvers.

Minimal reproduction of the problem with instructions

The resolver works fine, and the exceptions reaches the response in the graphiql request.

This is the classes i use

@Resolver()
export class UserResolver {

    @Mutation('users')
    @UseFilters(HttpException)
    public async findUsers() {
        throw new InternalServerErrorException();
    }
}

@Catch()
export class HttpException implements ExceptionFilter {
    catch(exception: any, host: ArgumentsHost) {
        console.log('Cathing exception');
    }
}

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

Environment

Nest version: X.Y.Z

 
For Tooling issues:
- Node version: 9.4.0
- Platform:  Linux

Others:

[Drago96]

I believe this feature has been added with version 6.0.0 . You can find a working example in the docs here https://docs.nestjs.com/graphql/tooling#exception-filters

[lock[bot]]

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.