enhancement/optimize graphql server for production builds #1277
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue
N / A
Noticed that tests were intermittently failing due to an extra -cache.json file being generated. (i think maybe it was always there?)
Not really causing any harm, but extra work nonetheless, and threw off our tests. Seems like an
IntrospectionQuery
is being run and causing the extra cache file to be generated, perhaps something only manifesting now since this introspection seems to happen on a polling interval?Summary of Changes
Ultimately I had to resort to just blocking the
IntrospectionQuery
operation since even turningintrospection
off and disabling the playground would cause weird Apollo server errors or would make the call anyway. 🤷♂️