Allow passing custom gql schema function to ParseServer#start options #6762
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
Codecov Report
@@ Coverage Diff @@
## master #6762 +/- ##
==========================================
- Coverage 93.91% 93.87% -0.05%
==========================================
Files 169 169
Lines 12029 12484 +455
==========================================
+ Hits 11297 11719 +422
- Misses 732 765 +33
Continue to review full report at Codecov.
|
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 simple typecheck seems to be missing, which results in not being able to pass a custom "merging" function to the ParseGraphQLServer instance through ParseServer#start.
This section requires the passed custom graphql schema to be a function, however the line this PR alters prevents the usage of that section in its current revision.