Deprecate EventsGet in favor of EventsQuery without filters
#764
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
LiranCohen
force-pushed
the
lirancohen/events-get-for-events-query
branch
from
07ee774 to
0f1ee0b
Compare
LiranCohen
requested review from
mistermoe,
csuwildcat and
thehenrytsai
as code owners
LiranCohen
force-pushed
the
lirancohen/events-get-for-events-query
branch
from
fe345c4 to
0f1ee0b
Compare
thehenrytsai
approved these changes
Jun 20, 2024
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.
EventsGetwas used for sync beforeEventsQuerywas made available, which allows filtering events/messages vs simply getting all of them.This PR removes the
EventsGetinterface method and removes the restriction inEventsQueryto allow querying without any filters.