This repository has been archived by the owner on Sep 3, 2021. It is now read-only.
Exclude subscription type when augmenting queries #323
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.
Subscriptions are not yet supported, but it is still possible to implement it manually, see #164 (comment)
I tried to do this for a personal project, and was met with the following error message:
The problem is that the
Subscription
type is interpreted by theaugmentResolver
as a generic type, likePost
in the example below.A quick fix was to exclude
Subscription
in the config, like so:But this shouldn't really be necessary, since
Subscription
is a special type, likeQuery
andMutation
.And this pull request, just automatically excludes subscription types, until subscriptions are properly implemented, for those who want to implement subscriptions manually.