You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2024. It is now read-only.
Unfortunately, sorting by departure or arrival times, if searching across multiple dates, isn't useful. Times across two different dates are intermingled, sorted SOLELY by the time column. To wit:
Good point. So, you think the right behavior is to implicitly sort first by date, then by time? Or maybe you should be able to specify a primary and secondary sort column to do it explicitly?
Hrm... I just thought of the use case for it working as it does now: "I know I want to leave in the morning, but I don't care which day." :-/
I can see this working two different ways. Actually, it'll "work" the same both ways, just two different ways for the user to see it. Option one is as you said, primary and secondary sort, explicitly offered that way via arguments. So -s depart_time is as it works now and -s depart_date depart_time is as I was looking to have it done. The other is to give a name to each type of sort: -s depart_time vs -s depart_order or something like that. Under the hood, they'd work the same, though.
Unfortunately, sorting by departure or arrival times, if searching across multiple dates, isn't useful. Times across two different dates are intermingled, sorted SOLELY by the time column. To wit:
The text was updated successfully, but these errors were encountered: