Skip to content

Keep route summaries with timelines and simplify tracking layout - #317

Merged
OziinG merged 1 commit into
mainfrom
codex/fix-route-timeline-summary
Oct 1, 2026
Merged

OziinG merged 1 commit into
mainfrom
codex/fix-route-timeline-summary

Conversation

@OziinG

@OziinG OziinG commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

The route summary table (name, driver, start time and totals) belongs with the timeline. Moving only the timeline left that table below all orders. Place the unchanged summary table immediately after the timeline in standalone, saved child, and All routes views. Tracking visibility remains unchanged.

Remove the Route overview heading and its explanation row. Remove the four primary metrics’ vertical dividers and side indentation; equal column gaps align both rows. Keep the existing evidence disclosure and long-value wrapping.

Validation: 112 route tests, build, typecheck, scoped ESLint, public URL guard and diff check pass. Real-component browser assertions verify map → timeline → summary → orders in all three route views and absence of that summary table on Tracking. At 390/681/1440px, the Tracking summary has no horizontal overflow; its primary metrics have zero left border/padding and aligned column starts. Independent review approved.

Manual K-food deployment follows exact-main CI. No data, route actions, map height or Shopify records change.

Keep the existing route summary table immediately after its timeline and before orders. Remove the tracking summary heading row and primary metric dividers so wrapped rows align without extra height.

Confidence: high
Scope-risk: narrow
Tested: 112 route tests; build; typecheck; scoped lint; browser ordering in standalone, child and All routes; tracking at 390/681/1440px
@OziinG
OziinG merged commit b02b8f2 into main Oct 1, 2026
2 checks 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.

1 participant