Release v15.35.8
Summary
ReadModelScenario, the in-process read model testing harness, diverged from the real Chronicle runtime in a few ways that could let read model specs pass while the modeled behavior was actually wrong — and could hide reducer bugs entirely. These fixes bring it in line with runtime behavior for read model removal, reducer initial state, reducer failures, and event sequence numbers.
Fixed
ReadModelScenarionow reflects a root-level removal: a class-level[RemovedWith](and[ClearWith]on a[Nested]) makesInstanceresolve tonullinstead of returning the stale pre-removal state.ReadModelScenarionow seeds reducer-backed read models with the provided initial state instead of always starting the reducer fromnull.ReadModelScenarionow surfaces a failing reducer (throwingReducerFailed) instead of returning the reducer's partial state as a successful result.ReadModelScenarionow assigns increasing per-event sequence numbers to a reducer'sEventContextinstead of the first sequence number for every event.