Miler rider app: surface system, visible design language, backend lifecycle
Design system - MilerSurface ladder (canvas → working → raised → floating) with MilerPanel as layer 1; canvas moved to #DEE3EA so white separates at 1.290:1. - Visible vocabulary applied across Home, Deliveries, Activity, Account and the sheets: hero heads (tabular numeral + small caption, clamped at 1.3x), canvas wells for anything that opens, small filled tags for shelf labels, demoted placeholders. Recorded in DESIGN_SYSTEM.md §6. - One icon family: 222 Material glyphs migrated to Lucide; none left outside lib/xpress. - Colour semantics corrected: amber only for what is genuinely owed, brand red reserved for the live stop, disabled primaries go neutral rather than pale. Data and lifecycle - lib/data/lifecycle.dart reads mutations for what they prove; route_order.dart makes admin sequence the single ordering authority; service_day.dart, and stop_area.dart rewritten against live Coimbatore addresses (digit-token stripping, city stoplist, street suffixes, stammer collapse). - countLabel states the load once, in bags. Testing - 1440 tests passing; golden shot harnesses for Home, Deliveries, Activity, sheets and verify, with test/failures/ now gitignored (diff debris). - New pins: home_gutter_test, stop_area_test, plus updated structural bounds. Note: this commit also carries pre-existing working-tree deletions that were present before this work (API_SPEC.md, README.md, demo test fixtures). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -158,9 +158,31 @@ class RouteMetricsHelper {
|
||||
Map<String, dynamic> stop, {
|
||||
double? riderLat,
|
||||
double? riderLng,
|
||||
// ── Which end of the journey is "the stop"? ──
|
||||
//
|
||||
// This always read the pickup pair, which on the delivery leg measures
|
||||
// the ride BACK to the kitchen the rider just left — the number grew as
|
||||
// he approached the customer's door. The caller knows which leg it is
|
||||
// rendering (the queue asks `MilkRun.workingKind`); this function cannot,
|
||||
// so the leg arrives as a flag. Default false keeps every pickup-leg
|
||||
// caller — Home's cards, the group nodes — exactly as it was.
|
||||
//
|
||||
// A delivery row whose payload carries no drop pair still falls back to
|
||||
// the pickup pair: on a hyperlocal round the stop IS the customer's
|
||||
// address in many payloads, and a wrong-ish number beats a dash the
|
||||
// rider cannot plan with.
|
||||
bool toDrop = false,
|
||||
}) {
|
||||
final stopLat = _toDouble(stop['pickuplat'] ?? stop['PickupLat']);
|
||||
final stopLng = _toDouble(stop['pickuplon'] ?? stop['PickupLon']);
|
||||
double stopLat = _toDouble(stop['pickuplat'] ?? stop['PickupLat']);
|
||||
double stopLng = _toDouble(stop['pickuplon'] ?? stop['PickupLon']);
|
||||
if (toDrop) {
|
||||
final dLat = _toDouble(stop['droplat'] ?? stop['DropLat']);
|
||||
final dLng = _toDouble(stop['droplon'] ?? stop['DropLon']);
|
||||
if (dLat != 0 && dLng != 0) {
|
||||
stopLat = dLat;
|
||||
stopLng = dLng;
|
||||
}
|
||||
}
|
||||
|
||||
final fromLat = (riderLat != null && riderLat != 0)
|
||||
? riderLat
|
||||
|
||||
Reference in New Issue
Block a user