Skip to content

reactive-tasks 1.2.0 - #5

Merged
rinekri merged 1 commit into
masterfrom
feature/1.2.0
Nov 10, 2026
Merged

rinekri merged 1 commit into
masterfrom
feature/1.2.0

Conversation

@rinekri

@rinekri rinekri commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

reactive-tasks 1.2.0. Source compatible with 1.1.0; no new RunState value.

Restores two remo semantics that apps lost when migrating from remo 1.2.0 / 9.0.1.

Added

  • finishedStates(handle, replayLast = false): Flow<JobState>: finished (success or error) states only. With replayLast = true it replays the last finished job even while another job of the task runs. Never completes on job cancellation. Equivalent of remo results(replayLast).
  • runningStates(handle): Flow<Boolean>: isRunning(handle) as a flow. Goes back to false after a job is cancelled (remo reset its state to Idle; jobStates emits nothing on cancel, so progress built on it stayed true).

Changed

  • successResults(handle, replayFinished = true) and errors(handle, replayFinished = true) replay the last finished job during a re-run, then filter it, as remo successResults/errors(replayLast) did. In 1.1.0 a subscriber arriving during a re-run got nothing until the current run finished.

Tests
JVM and Android host: SchedulerTest 21/21, ObserveStateChangesTest 18/18 (7 new), ConcurrentCollectionsTest 5/5. iOS targets compile; iOS tests run on CI only.

- finishedStates(handle, replayLast): finished states only, replays the
  last finished job even while another one runs (remo results(replayLast))
- runningStates(handle): isRunning as a Flow, goes false after a cancel
  (remo JobFlow.state for progress)
- successResults/errors(replayFinished = true) replay the last finished
  job during a re-run, then filter, as remo did
@rinekri
rinekri merged commit 3102b96 into master Nov 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants