uhryniuk
a14f5b0134
Route plans are their own entity (RoutePlan/Waypoint, schema v3), never joined into ride totals or the rides list. RoutePlanRepository recomputes straight-line distance after every waypoint mutation. RoutePlannerScreen supports tap-to-add, tap-to-delete, and hand-rolled drag-to-move via MapCamera's screen/latlng conversions. Fixed a real bug found by testing: FlutterMap's initialCenter/initialZoom are read once at construction, so building the map before the waypoints stream's first emission froze the camera on null-island. Also documents a genuine ten-minute test hang traced to Stream.first on a Drift watch() query inside testWidgets, which needs a pump-driven Timer that flutter_test's fake zone never advances on its own.
73 lines
3.7 KiB
Markdown
73 lines
3.7 KiB
Markdown
# v3 tickets
|
|
|
|
One file per feature, in the shape that worked for v2: Goal · Context · Design ·
|
|
Implementation · Acceptance criteria · Tests · Risks · Out of scope. Written before
|
|
implementing, so the risks are on paper before they are walked into.
|
|
|
|
Menu, not a commitment. Nothing here is scheduled.
|
|
|
|
**Everything in v3 is buildable with no server.** Group rides, accounts and paid cloud
|
|
backup are v4 — see [../BACKLOG.md](../BACKLOG.md).
|
|
|
|
> **Before starting anything:** [../port/REAL-RIDE-CHECKLIST.md](../port/REAL-RIDE-CHECKLIST.md).
|
|
> The port has never recorded a real ride, and item I3 may still force a change of GPS
|
|
> engine — which would land underneath several of these tickets.
|
|
|
|
## The tickets
|
|
|
|
| # | Ticket | Size | Depends on | Status |
|
|
|---|---|---|---|---|
|
|
| [V3-01](V3-01-activity-type.md) | Activity type per ride | M | — | Done |
|
|
| [V3-02](V3-02-settings-screen.md) | Settings screen | S | — | Done |
|
|
| [V3-03](V3-03-units.md) | Distance and speed units | S | V3-02 | Done |
|
|
| [V3-04](V3-04-live-map.md) | Live map on the recording screen | M | — | Done |
|
|
| [V3-05](V3-05-mounted-mode.md) | Mounted (handlebar) mode | M | V3-04 | Done |
|
|
| [V3-06](V3-06-notification-stats.md) | Live stats in the notification | S | — | Done |
|
|
| [V3-07](V3-07-route-drawing.md) | Route drawing (pins, straight lines) | M | — | Done |
|
|
| [V3-08](V3-08-road-routing.md) | Road-snapped routing and ETA | L | V3-07, V3-01 | Not started |
|
|
| [V3-09](V3-09-route-following.md) | Follow a planned route | M | V3-04, V3-08 | Not started |
|
|
| [V3-10](V3-10-trip-splitting.md) | Trip splitting | S | — | Not started |
|
|
| [V3-11](V3-11-offline-tiles.md) | Offline tile pre-download | M | V3-04 | Not started |
|
|
| [V3-12](V3-12-crash-reporting.md) | Crash reporting | S | — | Not started |
|
|
| [V3-13](V3-13-real-ride-measurements.md) | Real-ride measurements | M | **riding** | Not started |
|
|
| [V3-14](V3-14-gpx-interop.md) | GPX interoperability | S | V3-01 | Not started |
|
|
| [V3-15](V3-15-auto-pause.md) | Auto-pause | M | V3-13 *(gated)* | Not started |
|
|
| [V3-16](V3-16-visual-identity.md) | Visual identity | M | V3-04, V3-05 | Not started |
|
|
|
|
## Dependencies
|
|
|
|
```
|
|
V3-01 ──┬────────────► V3-08 ──► V3-09
|
|
└──► V3-14 ▲
|
|
V3-07 ──────► V3-08 │
|
|
V3-02 ──► V3-03 │
|
|
V3-04 ──┬──► V3-05 ──┬───────┘
|
|
├──► V3-11 └──► V3-16
|
|
└──► V3-09
|
|
V3-13 ──► V3-15 (gate: may close unbuilt)
|
|
|
|
no dependencies: V3-01 · V3-02 · V3-04 · V3-06 · V3-07 · V3-10 · V3-12
|
|
```
|
|
|
|
## Three that carry more weight than their size suggests
|
|
|
|
**V3-01** ships the port's **first real migration**. The destructive fallback is gone, so
|
|
getting `addColumn` plus a v1-database test right matters more than the feature does —
|
|
V3-07 and V3-09 both add migrations behind it.
|
|
|
|
**V3-08** forces a routing-engine decision with ongoing cost and vendor implications.
|
|
Behind a `RoutingService` interface, mirroring what `LocationSource` did for GPS.
|
|
|
|
**V3-13** is not code. It answers the three questions that have been open since v2, and
|
|
**V3-15 may close unbuilt** as a result — a legitimate and probably likely outcome.
|
|
|
|
## Suggested order, if starting cold
|
|
|
|
1. **V3-01** — proves the migration path while the stakes are low, and unblocks V3-08/14
|
|
2. **V3-02 + V3-03** — small, self-contained, gives V3-01 a home
|
|
3. **V3-04** — the most visible change, and the gateway to four other tickets
|
|
4. **V3-07** — entirely independent; useful on its own before the routing decision
|
|
5. **V3-13** — as soon as there is a ride to measure
|
|
|
|
V3-12 is a good filler at any point. V3-16 should wait until the screens stop moving.
|