This repository was archived by the owner on Mar 7, 2018. It is now read-only.
Implement publishEvents resolver #12
Merged
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 pull request implements the
publishEvents
resolver inMessageSchema
mentioned in project-fortis-spark#17 which is the same as the client-piece mentioned in project-fortis-spark#30The implementation is straight forward:
I've also set up a test EventHub for everyone to play around with the implementation. Use the following environment settings:
Sample mutation for graphiql.
Here you can see messages being sent to the EventHub from GraphQL: