Trey t
0c4777216e
Single unified search at the app root. TO is optional: filled goes through
/route (connections); blank flips to /departures with a time-window picker
("Where can I go?"). Same per-leg load card detail screen for any tap, so
direct flights and multi-stop connections share the same UX.
- Drop ContentView entirely (favorites + browse + entry cards). FlightsApp
instantiates RoutePlannerView directly.
- Delete WhereToGoView; DepartureLegRow is inlined into RoutePlannerView
as the where-can-I-go result row.
- SearchRoute enum trimmed to just the cases DestinationsListView still
references and moved to its own file (Models/SearchRoute.swift).
Sort bar moved out of the controls cards into a dedicated row between the
Search button and the results — only visible once results exist. Switched
from segmented to dropdown menu picker. Options narrowed to the four
the user asked for: Departure Earliest / Departure Latest / Fewest Stops
/ Most Stops in connection mode, just the two time-based options for
where-can-I-go (single-leg, stop-count is meaningless). All sorts apply
client-side; upstream still gets `departure_time` for a stable base order.
Two real bugs fixed in connection search:
- Past flights weren't filtered. Same-day searches return mostly already-
departed itineraries because the API sorts earliest-first. Added a
`firstDeparture > now` filter applied before sort. Header surfaces the
dropped count ("12 itineraries · 38 already departed"). When every
result is past, the error message says so explicitly instead of going
blank.
- 100-result limit was way too low for hub→hub with maxStops:2 — the
combinatorial explosion of valid permutations filled the cap with
morning flights and never reached afternoon. Bumped to 500.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
14 lines
573 B
Swift
14 lines
573 B
Swift
import Foundation
|
|
|
|
/// Navigation destinations used by `DestinationsListView`.
|
|
///
|
|
/// Originally defined alongside `ContentView`, which is now removed.
|
|
/// `RoutePlannerView` is the home and uses sheet-based detail presentation
|
|
/// rather than `navigationDestination(for:)`, so the only remaining caller
|
|
/// is the orphan path inside DestinationsListView. The enum stays so that
|
|
/// view still compiles in case it gets re-introduced as a feature later.
|
|
enum SearchRoute: Hashable {
|
|
case destinations(Airport, Date, Bool)
|
|
case routeDetail(Airport, Airport, Date)
|
|
}
|