Cloud: correctly apply skipped episode state when re-adding a show #1112
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.
When introducing plays a regression was introduced where the skipped status would not get applied to episodes when adding a show and downloading episode state from Cloud.
The database update method required plays to be not null, but for skipped episodes plays were not explicitly set to
0
but left atnull
.This resolves this issue and refactors the build and apply methods to facilitate testing. This adds tests for common cases, also when downloading changes ("syncing").