Christoph Zwerschke
Christoph Zwerschke
@kevinvalk thanks for the feedback. In fact if you're using a lot of caching and the work starts to become CPU bound then the price for async can be heavy...
Thanks for the valuable input @QSHolzner
Hi @alessandrolulli. Can you check whether the [@defer/@stream](https://github.com/graphql/graphql-js/blob/main/website/docs/tutorials/defer-stream.md) functionality of GraphQL.js 17.0.0a2 which is already contained in the main branch of GraphQL-core would solve your problem?
Note that the [@defer/@stream](https://github.com/graphql/graphql-js/blob/main/website/docs/tutorials/defer-stream.md) functionality of GraphQL.js 17.0.0a2 is now included in GraphQL-core 3.3.0a3.
Hi @abhinand-c , and thank you for reporting and providing a fix. May I suggest that next time you create an issue before posting a PR ? We can then...
No worries @abhinand-c it's all well. GraphQL.js is our upstream project. The guidelines for contributing to GraphQL.js are [these](https://github.com/graphql/graphql-js/blob/main/.github/CONTRIBUTING.md) if you want to create a PR there, but here we...
Thanks for reporting. Will look into this when I have more time, probably only after releasing 3.3. It would be helpful if you could post example code with dummy data...
Yes, should be fixed in 3.3.0a5.
Thanks for the feedback @mat-sop. Let's first simplify the problematic SDL a bit to get to the core of it: ```graphql """Example 1""" type Query { field(recursiveInput: RecursiveInput): String }...
Sure, PRs of that kind are always welcome.