nullswan
nullswan
Released in 3.0.0
Do you think you can provide a reproduction @randomiser ?
Archiving. Feel free to open again.
If you push the error to the context, the query won't be canceled. Instead, it will still be processed and go through the entire flow until it reaches the next...
> FWIW, graphql-js's reference implementation seems to honor this: https://github.com/graphql/graphql-js/blob/e15c3ec4dc21d9fd1df34fe9798cadf3bf02c6ea/src/graphql.ts#L122 Indeed, request cancellation is not supported. Parse, return errors, Validate, return errors. But that is too late. Let's take maxTokens...
I'll be happy to review a merge request about this topic ! 🥳
Nice catch, feel free to open a MR @ejkg :)
Hey @rupert648, `fragmentRecursionCost` is a deprecated field, initially applied when a fragment has already been visited. You can reduce the `depthCostFactor` if you wish to treat all fragment as inline...
We already support a lot of configuration parameters. Any example of calculation function?
Archiving. Feel free to open again.