Skip to content

fix: include Rowes Wharf stop when filtering by ferry route_type#1020

Open
khansen-mbta wants to merge 1 commit into
masterfrom
kh/include-rowes-wharf
Open

fix: include Rowes Wharf stop when filtering by ferry route_type#1020
khansen-mbta wants to merge 1 commit into
masterfrom
kh/include-rowes-wharf

Conversation

@khansen-mbta
Copy link
Copy Markdown
Contributor

Summary of changes

Asana Ticket: 🐛 🍎 API output not as expected (causes inability to create alerts for Rowes Wharf)

Previously, the Rowes Wharf stop was not being included in the API response for /stops?filter[route_type]=4. The routes_by_stops_and_direction helper in route_patterns_at_stop.ex defaulted to select only canonical routes for a given stop ID. This passes an option to check non-canonical routes since some ferry routes do not have patterns marked as canonical. The response now includes Rowes Wharf as well as the previously returned stops as well.

@khansen-mbta khansen-mbta requested a review from a team as a code owner May 26, 2026 14:52
@khansen-mbta khansen-mbta requested review from rudiejd and removed request for a team May 26, 2026 14:52
@khansen-mbta khansen-mbta force-pushed the kh/include-rowes-wharf branch from 2c6ef1f to 6f322ab Compare May 26, 2026 15:13
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.

1 participant