Added new API Mesh Custom Resolver sample.#13
Open
GabrielRanghetti wants to merge 1 commit into
Open
Conversation
Collaborator
|
Hello @GabrielRanghetti Thank you for your contribution. Can you please just push the mesh config and the resolvers related to it instead of the whole local workspace? It makes it really easy for everyone to clone and continue if its just the mesh config and the related files. |
This file contains hidden or 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
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.
Description
Added two new fields to the schema using a custom resolver. The data for these fields will be retrieved from Trevorblades GraphQl.
Related Issue
None
Motivation and Context
Accelerates onboarding to API Mesh Custom Resolvers and improves developer experience.
How Has This Been Tested?
Tested by running the GraphQl query with the new two fields.
Screenshots (if appropriate):
Types of changes
Checklist: