Allow configuration of the ofType introspection depth
#4317
Conversation
…ery depth This allows for a better configuration in case the server restricts the maximum query depth.
| @@ -52,6 +61,7 @@ export function getIntrospectionQuery(options?: IntrospectionOptions): string { | |||
| schemaDescription: false, | |||
| inputValueDeprecation: false, | |||
| oneOf: false, | |||
| typeDepth: 9, | |||
There was a problem hiding this comment.
so this default is a breaking change. If we want this to land in v16 then we should do Infinity and in v17 we can restrict the limits.
There was a problem hiding this comment.
Why is that a breaking change? The behaviour is exactly the same as before. Infinity would lead to an infinite recursive loop.
There was a problem hiding this comment.
@saihaj I think you may have misunderstood which depth this relates to - it's the ofType { ofType { ofType { ... } } } depth of the generated query. We couldn't set that to infinity.
benjie
changed the title
benjie
changed the title
ofType introspection depth
Co-authored-by: Benjie <[email protected]>
|
@benjie Thanks for the suggestions. I've commited them my branch. I think for the scope of this PR that is the right move. I'd also like to take this as an opportunity to discuss formatting the introspection query. I think it would be simpler to just keep the query in one line, without indentions. This could clean up the code and save a few byte over the wire. It would of course reduce the readability. Maybe we can document the query better, so that would become less of an issue. |
This allows for a better configuration in case the server restricts the maximum query depth.