Skip to content
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

Merged
merged 18 commits into from
Jan 21, 2025

Conversation

KaylaBrady
Copy link
Collaborator

@KaylaBrady KaylaBrady commented Jan 15, 2025

Summary

Ticket: 🤖 | stop + trip details | barebones UX

What is this PR for?

This is a first step in getting the barebones UX trip details.

  1. Rename filter => stopFilter and add tripFilter
  2. Rework navigation to pass around SheetRoute instead of NavBackStackEntry. This made it easier to read the filters that are set on the stop details pages.
  3. Copy setStopFilter logic from iOS.
    iOS
  • If you added any user-facing strings on iOS, are they included in Localizable.xcstrings?
    • Add temporary machine translations, marked "Needs Review"

android

  • All user-facing strings added to strings resource
  • Expensive calculations are run in withContext(Dispatchers.Default) where possible

Testing

What testing have you done?

  • Added unit tests
  • Ran locally and confirmed navigation between nearby transit & stop details still works as expected
    • Note: the back button now works as a close button since on iOS there is no longer a back button on stop details.

@KaylaBrady KaylaBrady requested a review from a team as a code owner January 15, 2025 14:23
@KaylaBrady KaylaBrady requested a review from BrandonTR January 15, 2025 14:23
Copy link
Contributor

@BrandonTR BrandonTR left a 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
Copy link
Contributor

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?

Copy link
Collaborator Author

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.

@KaylaBrady KaylaBrady force-pushed the kb-android-trip-details-barebones branch from 17d504c to 08171ca Compare January 17, 2025 17:08
@KaylaBrady KaylaBrady force-pushed the kb-android-trip-details-barebones branch from 08171ca to 4436968 Compare January 21, 2025 15:57
@KaylaBrady KaylaBrady force-pushed the kb-android-trip-details-barebones branch from a96d9d8 to 6345929 Compare January 21, 2025 19:21
@KaylaBrady
Copy link
Collaborator Author

Accidentally overwrote merging #661 into this branch with a force-push. Manually re-applied merge

@KaylaBrady KaylaBrady merged commit bb9a911 into main Jan 21, 2025
7 checks passed
@KaylaBrady KaylaBrady deleted the kb-android-trip-details-barebones branch January 21, 2025 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants