chore: Unifiy implementation of State #1586
Merged
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.
linked #1410
Refactoring
Unify implantation of the
State
to always be a "subscription on anUpdateFeed
" no matter the type of the updates defined on it.What is the current behavior?
When a state was created using
StateUpdateKind.Persistent
(only for pagination), it was using a completed (more recent) implementation.What is the new behavior?
No matter the defined
StateUpdateKind
,State
now uses the same implementation (which can be summarized as "a state is aFeedSubscription
made on anUpdateFeed
")PR Checklist
Screenshots Compare Test Run
results.