Deprecate SubscriptionArgs and broaden ExecutionArgs #3306
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
yaacovCR
force-pushed
the
broaden-execution-again
branch
from
8fd02e7
to
0b2bfb8
Compare
This was referenced Oct 11, 2021
IvanGoncharov
added
the
PR: feature 🚀
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.
Broaden ExecutionArgs to include all properties within SubscriptionArgs. Retain the SubscriptionArgs type for backwards compatibility, to be removed in the next major version.
This allows for better unification of subscription operations alongside queries and mutations as additional targets of execution.
Repeat of #3295