Add GraphQL field extension with field resolver function #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dmitriy Lazarev <[email protected]>
taras
approved these changes
Feb 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
In Backstage GraphQL plugin we query Catalog API to get entities that matched to specific filter, then we have to resolve each entity to GraphQL Node, but in our fields' resolvers we call data loader to fetch entity (again) and get field's value. We could improve and get rid of unnecessary
getEntitiesByRefscall if we are able resolve fields right away.Approach
Utilize GraphQL Extensions to store field's resolver, that accepts
{ id, entity }node's id and source object and returns needed field's value