Merged
Conversation
The `app.graphql.failOnUnmapped` property defaults false, but if set true, will cause app startup to fail if any part of the GraphQL schema is not mapped to an implementation. This was Kickstart's behavior.
"Is this mine" is a common question in the client, so expose that answer directly, rather than forcing a client-side join. This was trivial with Flux, but with Apollo it's trickier.
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
1 participant
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.
"Is this mine" is a common question in the client, so expose that answer directly, rather than forcing a client-side join. This was trivial with Flux, but with Apollo it's trickier.
Also allow opting in to startup failures if the graphql schema is not fully mapped onto Spring components.