-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix: Fix issue with non-CR routes showing up in nearby transit for stops that also serve distant CR #116
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Coverage of commit
|
Coverage of commit
|
EmmaSimon
commented
Apr 11, 2024
KaylaBrady
approved these changes
Apr 11, 2024
Coverage of commit
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Ticket: Nearby transit shows non-CR routes between 0.5 and 1 mile away
We separately fetch CR stops with a 1 mile radius, and any other stops with a 0.5 mile radius, but we were also returning all sibling stops of any mode when a stop was in range. This was leading to subway routes being bubbled to the top, even though they were only served at more distant commuter rail stops. This change only returns sibling stops of commuter rail if those siblings are also commuter rail.
This was initially done on the frontend in mbta/mobile_app#126
Testing
Fix breaking tests, the existing base integration test already had a case where (shuttle) bus stops were being included, now the test checks explicitly that they're excluded.