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

feat(iOS): Combined stop details - display scheduled trips #601

Merged
merged 8 commits into from
Jan 2, 2025

Conversation

EmmaSimon
Copy link
Contributor

@EmmaSimon EmmaSimon commented Dec 19, 2024

Summary

Ticket: Combined Stop + Trip Details: Show trip details when there's no predicted vehicle

Stacked onto #599

Display trip schedules if no vehicle or predictions exist. For any non-ferry trips, also allow tapping on the trip card to open an explainer cover that shows some text explaining the state.

Simulator Screenshot - iPhone 15 - 2024-12-18 at 20 49 22 Simulator Screenshot - iPhone 15 - 2024-12-18 at 20 49 44 Simulator Screenshot - iPhone 15 - 2024-12-18 at 20 51 44

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

Testing

Updated existing tests, added new tests for new behavior.

@EmmaSimon EmmaSimon requested a review from a team as a code owner December 19, 2024 15:12
@EmmaSimon EmmaSimon requested review from boringcactus and removed request for a team December 19, 2024 15:12
@EmmaSimon EmmaSimon force-pushed the es-combined-stop-schedules branch 2 times, most recently from 174c214 to e47f71d Compare December 19, 2024 16:49
Copy link
Member

@boringcactus boringcactus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the architecture you've gone with here.

Base automatically changed from es-stop-details-page-vm-refactor to main December 19, 2024 18:54
This makes it easier to make the changes for the future first stop
behavior when we need to do things more complicated than checking if
the vehicle exists, and ensures it can never break the existing trip
details page.
@EmmaSimon EmmaSimon force-pushed the es-combined-stop-schedules branch from e47f71d to 856b89c Compare December 19, 2024 18:57
@EmmaSimon EmmaSimon merged commit d9b25d3 into main Jan 2, 2025
7 checks passed
@EmmaSimon EmmaSimon deleted the es-combined-stop-schedules branch January 2, 2025 15:26
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