feat: Add aggregate visibility state changed callback #1385
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
To fix #1343, I believe a new callback that reports the latest visibility state(s) for that
EpoxyVisibilityItemshould be introduced. Without this aggregate information, client will need to somehow batch theVisibilityStateby themselves for 1vi.updatecycle. To avoid object allocation, instead of usingdata class AggregateVisibilityStateI just expose the properties fromEpoxyVisibilityItemas read-only.Alternatively to fix #1343, we could change the ordering of
VisibilityStateemission ononVisibilityStateChanged. Please let me know if that's preferred.Test
I have included comparing the aggregate visibility state in
EpoxyVisibilityStateTrackerTest.