Skip to content

feat: Have Foxboro Event Service timetables default to Outbound - #3420

Merged
joshlarson merged 1 commit into
mainfrom
jdl/feat/have-foxboro-event-service-always-default-to-outbound
Aug 17, 2026
Merged

feat: Have Foxboro Event Service timetables default to Outbound#3420
joshlarson merged 1 commit into
mainfrom
jdl/feat/have-foxboro-event-service-always-default-to-outbound

Conversation

@joshlarson

Copy link
Copy Markdown
Contributor

Scope

No ticket - I just got confused when I looked at the Foxboro Event Service timetable for August 17, which does have service, and it showed no service... well, we pretty much don't schedule return service, which is typically inbound, so it's more useful to show the service that we do have scheduled, which is outbound.

Screenshots

How to test

Look at the Foxboro Event Service timetable for August 17. It'll show the scheduled trips even if you look before the default direction changes to Outbound at 2PM.

If you're looking after 2PM, you can pretend that it's before 2PM by hacking the definition of "now" to be whatever time you want.

def now(), do: ~N[2026-08-14T12:00:00] |> Timex.to_datetime("America/New_York")

@joshlarson
joshlarson requested a review from a team as a code owner August 14, 2026 19:58
@joshlarson
joshlarson requested a review from jlucytan August 14, 2026 19:58
@joshlarson
joshlarson enabled auto-merge (squash) August 14, 2026 19:58
@joshlarson
joshlarson merged commit 3667e23 into main Aug 17, 2026
44 of 45 checks passed
@joshlarson
joshlarson deleted the jdl/feat/have-foxboro-event-service-always-default-to-outbound branch August 17, 2026 18:20
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