Graph federation test #14
Open
Conversation
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
- there is now a films datasource that you can equally look up
- Attempted to merge the two schemas together and partially failing
- PersonFetcher is working with the other hard coded graphql service and correctly stitches the schemas together
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.
This should demonstrate what is required to get a GraphQL service up and running WITH a really basic API gateway.
It hooks into the main person service Java SpringBoot application AND a dummy hardcoded film database that links these people to films (this server is just using the Apollo server node JS framework). And the API gateway is able to successfully stitch the two schemas together.