Upgraded Voyager UI to latest version #205
Merged
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
rose-a
pushed a commit
to rose-a/server
that referenced
this pull request
Mar 23, 2020
* updated voyager to latest version * updated comments
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.
Hello!
We are using the Voyager UI middleware that is provided in this package and noticed that it wasn't grabbing our mutations. This change brings in the latest voyager package which now allows you to switch between your query and your mutations and subscriptions as well. It also allows you to jump between things a little more easily.
For the code itself, it's using the voyager sample that is in their repo, which is what i believe was being done prior as well, as it looks similar to the existing code.