@Context decorator undefined for property resolvers

I’m submitting a…

[x] Regression 

Current behavior

Given the following GraphQL resolver:

@Resolver('SearchResponse')
export class ShopFulltextSearchResolver implements Omit<BaseSearchResolver, 'reindex'> {
    constructor(private fulltextSearchService: FulltextSearchService) {}

    @Query()
    async search(
        @Ctx() ctx: RequestContext,
        @Args() args: SearchQueryArgs,
    ): Promise<Omit<SearchResponse, 'facetValues'>> {
        return this.fulltextSearchService.search(ctx, args.input);
    }

    @ResolveProperty()
    async facetValues(
        @Ctx() ctx: RequestContext,
        @Context() context: any,
    ): Promise<Array<{ facetValue: FacetValue; count: number }>> {
        return this.fulltextSearchService.facetValues(ctx, context.req.body.variables.input);
    }
}

• the search method resolves a top-level query
• the facetValues method resolves a property of the SearchResponse type.

The context variable is undefined in the facetValues method.

Expected behavior

The context variable should contain the GraphQL context object, including the underlying express req object which I am making use of in the method body.

Note that this worked in Nest v6.0.2. After upgrading today to v6.0.5 it stopped working. Also, the @Context decorator appears to work as expected for top-level queries. Only property resolvers are broken.

Minimal reproduction of the problem with instructions

I put together this repo, which does not exactly reproduce the behaviour in my app but is close. In this case, the context object is empty, rather than undefined: https://github.com/michaelbromley/nest-issue-191-repro

Environment

Nest version: 6.0.5, graphql v6.0.4

[kamilmysliwiec]

Could you please check with @nestjs/graphql@6.0.5? Thanks for reporting

[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.