Dev/graphql #8
Merged
Dev/graphql #8
+1,698
−428
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
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.
Initial commit to support GraphQL, Far from finished, but it is a good start. Main issues after merging this PR are #6 #7 #9 and #10
Main commits are:
and the whole graphql things splitted into multiples commits. The graphql handler has been backported from vertx, we are just creating the graphql object on the fly instead of passing it at construct. The schema generator is also interesting, as it completely abstract the need of a backend for graphql users. We are automatically generating queries according to the indexes