Fix #38 #40 resolver in subscription #39
Open
Conversation
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
… set context dataLoaders in subscribe resolver
|
Any update on this? This is an awesome framework! would be a shame to stop updating it |
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 is to fix #38. Since there are no
CurrentRequest,CurrentResponseanddataLoadersin the context / container when it's subscription, the resolver will fail when it tries to access those from context inbuildCustomResolvers.Since
CurrentRequestandCurrentResponsecan beundefinedin subscriptions, I use the try catch to check if those 2 keys exists in theContainer.I also set
dataLoadersto an empty array in context when a new subscriber connects to server.