Skip to content

feat: New bespoke Harbor Loop Ferry timetable layout - #3432

Open
joshlarson wants to merge 11 commits into
mainfrom
jdl/feat/harbor-loop-ferry-layout
Open

feat: New bespoke Harbor Loop Ferry timetable layout#3432
joshlarson wants to merge 11 commits into
mainfrom
jdl/feat/harbor-loop-ferry-layout

Conversation

@joshlarson

@joshlarson joshlarson commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Scope

Asana Ticket: ⛴️ Render F10 schedule using the new bespoke F10 layout

Important

This feature is not behind a feature flag, so if this PR is merged, then on the next deploy, this will go live to riders. I think that's okay, but since most of the other timetable work I've done has been behind the new_timetables? feature flag, I wanted to make sure that this PR's non-flagged nature was clear.

Implementation

Note

I used 🤖 Copilot to generate the first commit of this PR. I've inspected the code and tests, and my tweaks and changes are the remaining commits.

  • Defines a couple of special assigns so that the Harbor Loop special case can load both timetables onto the page.
  • It uses the NewTimetable.timetable/1 component rather than Timetable.timetable/1 because the buttons on Timetable.timetable/1 can only work if there's a single timetable on the page (this is the entire reason that NewTimetable exists).

Screenshots

Screenshot 2026-08-18 at 7 24 47 PM Screenshot 2026-08-18 at 7 33 36 PM

How to test

Visit the Harbor Loop Ferry timetable page.

Try it out for different dates and browser widths.

A thing that I tried, just to validate a corner case that I admit would surprise me, was to change evening_schedules or morning_schedules to [] in the Boat-F10 assign_trip_schedules/1 clause. This is the result (Copilot's initial implementation was much less nice):

Screenshot 2026-08-27 at 8 43 43 AM

(I did this before the refactor in this commit, which removes the explicit morning/evening_schedules variables.)

Try out whatever else you think of!

@joshlarson joshlarson added the dev-blue Deploy to dev-blue label Aug 18, 2026
@joshlarson
joshlarson marked this pull request as ready for review August 27, 2026 12:59
@joshlarson
joshlarson requested a review from a team as a code owner August 27, 2026 12:59
@joshlarson
joshlarson requested a review from thecristen August 27, 2026 12:59
@smartling-github-connector smartling-github-connector Bot added the Not Ready for Translation Remove this when the PR is approved to trigger a Smartling translation job label Aug 27, 2026
@joshlarson joshlarson removed the Not Ready for Translation Remove this when the PR is approved to trigger a Smartling translation job label Aug 27, 2026
…-loop-ferry-layout (#3452)

* Translations delivered for PR#3432 on es-LA locale

* Translations delivered for PR#3432 on ht-HT locale

* Translations delivered for PR#3432 on zh-TW locale

* Translations delivered for PR#3432 on pt-BR locale

* Translations delivered for PR#3432 on fr-FR locale

* Translations delivered for PR#3432 on vi-VN locale

* Translations delivered for PR#3432 on zh-CN locale

---------

Co-authored-by: smartling-github-connector[bot] <165276057+smartling-github-connector[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dev-blue Deploy to dev-blue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant