DialogSelectViewHolderFactory update flow replay count to zero. #2080
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.
IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #2055
Description
QuestionnaireItemDialogSelectViewModel
is created as a shared ViewModel by activityViewModel() to share data betweenDialogSelectViewHolderFactory
andOptionSelectDialogFragment
.The ViewModel stays in memory after both fragments are destroyed as scope is activity.
When the view (DialogSelectViewHolderFactory) is launched again, QuestionnaireItemDialogSelectViewModel emits the previously buffered state because of replay value which is 1.
Alternative(s) considered
Another approach is to clear the ViewModel, but calling viewModelStore.clear() will clear all ViewModels.
Type
Choose one: Bug fix.
Screenshots (if applicable)
Checklist
./gradlew spotlessApply
and./gradlew spotlessCheck
to check my code follows the style guide of this project../gradlew check
and./gradlew connectedCheck
to test my changes locally.