apollo-server-core: Stop computing schema-derived data twice for non-gateway modes of operation #5757
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.
Running the schema-derived data provider in
SchemaManager.ts
can be expensive. Currently,SchemaManager
computes this twice for non-gateway modes of operation:SchemaManager
construction (as the caller expects errors to be caught early here).SchemaManager.start()
(as we naively call it withinSchemaManager.processSchemaLoadOrUpdateEvent()
).This PR:
SchemaManager.processSchemaLoadOrUpdateEvent()
to accept an optionalschemaDerivedData
argument, which (if provided) causes it to store that and skip calling the schema-derived data provider.start()
.Fixes #5729 .