Repository navigation
Add consolidations: one truck run for several shipments (#329) - #341
Merged
Merged
Conversation
A Consolidation groups shipments, usually for several customers, into one run with its own stops: every pickup before every drop, shared locations sharing a stop, and each shipment stop linked to the run stop serving it. Commands to create, update, add/remove shipments (draft only) and archive (a draft frees its shipments), a read model with projection and backfill, and a Consolidations list and detail page. A shipment links to its run. ShipmentStop's redundant (shipmentId) index is dropped to make room for (consolidationStopId), keeping it at three. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Slice 2 of #329: the Consolidation entity and page.
Consolidation,ConsolidationStop,ConsolidationShipment(uniqueshipmentId: one run per shipment),ShipmentStop.consolidationStopId, andConsolidationReadModel. Shipment gets no new index; ShipmentStop's redundant(shipmentId)index is swapped for(consolidationStopId).--only=consolidations), routes with schema blocks undershipments:write.Tested in the browser: a three-shipment, two-customer run; remove; duplicate refusal (400); missing id (404); archive freeing shipments. Full backend suite, tsc, lints pass.
Not yet: tracking (slice 3), drop reordering, map, cost allocation, per-customer Ship together, www.
🤖 Generated with Claude Code