Support for deep input graphs about graphql-js HOT 4 OPEN

I first misread the code. You seem to be affected the same.

One way to prevent the stack issue would be to transform many calls into generators

from graphql-js.

I think a max-depth guard as suggested in the linked issue sounds like a reasonable first step.

This project is open-source and so a PR to introduce “stack-free” execution should be welcome. One issue to consider is that the reference implementation should try to match the specification, which has a recursive design, but that’s not necessarily a complete block — It might depend on how transformative the PR would be. It could also depend on what performance profile the change has. If it comes with a significant improvement, for example, I imagine that it would be easier to advocate for its inclusion.

from graphql-js.

what do you think about the idea to use a rust parser for more performance and to easily synchronize the fix between both (and probably more) projects?

Rust can be compiled to webassembly so there is no compatibility issue here (and for python there are also bindings)

from graphql-js.

I lack knowledge of rust and can learn it just slowly (not much time)

from graphql-js.