-
Notifications
You must be signed in to change notification settings - Fork 1
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 #126
Closed
Closed
fix: Fix issue with non-CR routes showing up in nearby transit for stops that also serve distant CR #126
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f28f0a3
fix: Don't display non-CR routes further than .5mi
EmmaSimon 65dd143
test: Add test for filtering out distant routes
EmmaSimon 12c58b5
Merge branch 'main' into es-fix-nearby-mode-distances
EmmaSimon 9ca73ea
test: Fix iOS tests to be within stop range
EmmaSimon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This duplicates a value between the frontend and the backend, which seems inappropriate. How would you feel about a follow up where we remove 0.5 mile-ish threshold from the backend, and only make a single
stops
request with a 1 mile radius, then only have this distance threshold here. It's still weird to have the longer radius there and the shorter one here, but I think it's still better than this.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree it seems a little weird to have a longer radius filter on the backend and a shorter one on the frontend.
What do you think of keeping the filtering entirely on the backend? We could filter cr_included_stops to be only CR stops based on Stop.vehicle_type, which is a field we aren't currently parsing.
That was one approach we discussed at refinement but didn't capture in detail in the ticket, sorry for the missing context there!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! mbta/mobile_app_backend#116 I was initially going to implement it on the backend but couldn't see a clear path to doing so. I didn't realize that
vehicle_type
was a thing, that can maybe simplify some stuff on the frontend now that we have access to it.