Conversation
This has quite some duplicate code. The alert structure should be defined once as a GraphQL model and then handled by the proxy, so that the resolvers only need to return it. Also it's missing quite a lot of things and the readme is now wrong. Signed-off-by: Gregor Best <gbe@unobtanium.de>
It's working, the missing bit is subscriptions.
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.
The goal is to use GraphQL to fully specify querying and subscriptions, so that client code can be generated instead of having to hope that the JSON we ship kinda sorta matches.
The branch is almost unusable right now but will shape up over the next few days.