Loading
chore(datastore): add the container upstream position helpers part 2/15 (S17 Phase 6 plan: 42/42)
Why
The container store settles a list with pure functions over a slice, and their behaviour is reachable by unit test in ways a database is not: the settle has to lift a zero position that check_cvru_position_positive refuses to store.
They land ahead of their callers, which arrive in part 4, because they are separable and worth reading on their own.
The stack
Fifteen parts, each stacked on the last, each green on its own, reviewed in this order. Changed lines counts added plus deleted.
The delete guard in part 9 lands before the routes in part 11, so no window exists where a container association is writable without the refusal that protects it.
Related to #314 (closed)
Edited by Hayley Swimelar