Edouard Bougon
Edouard Bougon
Since this new version `"@nestjs/graphql": "10.1.1"`, it seems that the graphQL plugin doesn't introspect anymore the fields on `Args` class. I just updated my code with the version, and all...
Doing it right now
Hey @Hossein-s, is your solution working ? I'm really interested to add directive to field
@MichalLytek Do you have a public roadmap, or more information about this rewriting ?
Resolved for the moment. In my express middleware, I have to add this: ``` import { REQUEST_CONTEXT_ID } from '@nestjs/core/router/request/request-constants'; // ... use(req: Request, res: Response, next: NextFunction): void {...
I agree with @trubit , it's a breaking change. For example, I use guard to control access to my properties, with a AuthGuard and RoleGuard. Some properties are like "query",...
I agree with @pablor21, I encountered the same problem with multiple instance by request. May be it's a bug with Nest. So, for now, I use this solution: https://github.com/nestjs/graphql/issues/2#issuecomment-498968008
`brew install watchman` fixed the problem for me. https://github.com/cm-pliser-tdd-by-example/tdd-by-example-js/issues/10#issuecomment-361039205
Any update on types release ?
See the solution: https://github.com/Uniswap/interface/issues/7678#issuecomment-2021792144