Refactor: simplify and optimize ElasticGraph::GraphQL::Schema
.
#31
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.
::GraphQL::Schema#types
repeatedly. As reported in Performance regression in 2.4:Schema#types
is much slower to access repeatedly rmosolgo/graphql-ruby#5154, accessing#types
repeatedly can be quite slow (at least on 2.4.0 - 2.4.2). While it's been optimized in 2.4.3, there's no need to access it more than once. Previously, we accessed it in#lookup_type_by_name
; instead we can just use the type objects as we iterate over::GraphQL::Schema#types
a single time.#defined_types
method.#lookup_type_by_name
logic into#type_named
.