-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(android.NearbyTransitPage): navigation refactor to support trip filter #653
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Just one question
} | ||
|
||
fun setStopDetailsDepartures(departures: StopDetailsDepartures?) { | ||
_stopDetailsDepartures.value = departures | ||
} | ||
|
||
// TODO: Move these to separate Navigation utils helper |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this something you meant to do or something we should revisit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah thanks, I had meant to do this as part of this PR, but may leave it in place for now until I port over more of the navigation logic and see how it all fits together.
17d504c
to
08171ca
Compare
08171ca
to
4436968
Compare
a96d9d8
to
6345929
Compare
Accidentally overwrote merging #661 into this branch with a force-push. Manually re-applied merge |
Summary
Ticket: 🤖 | stop + trip details | barebones UX
What is this PR for?
This is a first step in getting the barebones UX trip details.
SheetRoute
instead ofNavBackStackEntry
. This made it easier to read the filters that are set on the stop details pages.setStopFilter
logic from iOS.iOS
android
withContext(Dispatchers.Default)
where possibleTesting
What testing have you done?