Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GraphQL context not correct in Guards when __resolveType handler is called

See original GitHub issue

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

When in a resolveType handler the context is wrongly resolved. Which makes me unable to use the graphql context in an global guard.

Expected behavior

Context to be resolved correctly

Minimal reproduction of the problem with instructions

https://github.com/JannesV/nestjs-issue-context

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

Need to use global guards

Environment


Nest version: 6.0.5

 
For Tooling issues:
- Node version: 8.11.4 \ 10.0  
- Platform:  Mac\ Linux

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:6 (2 by maintainers)

Top GitHub Comments

2reactions

kamilmysliwieccommented, May 11, 2019

It should be fixed in the @next version ($ npm i @nestjs/graphql@next). You will also have to update @nestjs/core to 6.2.0 ($ npm i @nestjs/core@6.2.0). Please, let me know if you face any issue.

1reaction

kamilmysliwieccommented, May 14, 2019

Published as 6.2.0 ($ npm i @nestjs/graphql@latest). You will also have to update @nestjs/core to 6.2.0 ($ npm i @nestjs/core@latest)