Allow using a query and cursor together when calling client.feed() #298
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 PR enables supplying a
cursor
value when using an unevaluated query withclient.feed()
.Description
This PR removes a check that prevented you from calling
client.feed()
with aquery
and acursor
. It is an unnecessary constraint, and event feeds will behave as you'd expect without this check.Motivation and context
This change allows you to resume at a given cursor while still passing in a query to generate the event source. Before this change, you'd need to first evaluate the query for the event source yourself before calling
feed
withcursor
.How was the change tested?
Change types
Checklist:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.