-
Notifications
You must be signed in to change notification settings - Fork 36
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
feat(core-utils): remove old query params handled by new mode selector #712
feat(core-utils): remove old query params handled by new mode selector #712
Conversation
I think this PR should be a breaking change PR. @miles-grant-ibigroup? |
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 think you should add a breaking change commit (or redo the PR with that commit being breaking change).
BREAKING CHANGE: removes old query parameters that are not needed
f89460e
to
e697697
Compare
Lost track of this PR for a bit, but I force pushed the breaking change commit. If you had this branch cloned, you'll need to delete it and pull it again. Or maybe force pull. |
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.
Can we delete more old params and get rid of the old routing types?
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.
The comment on lines 1-2 doesn't apply anymore and can be removed.
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 think the file should still be removed entirely, but probably not because of settingsselector anymore.
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.
We can probably remove the profile-only params that have routingTypes: ["PROFILE"]
(these are holdouts from before my time) such as startTime
, endTime
.
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.
In the same vein, I think we can get rid of routingTypes
, profileRewrite
alltogether. Thoughts?
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.
Yes! I was worried someone was using those, like TriMet, but I think you're right that we can remove them.
I deleted a lot more of the query parameters, but that caused some problems in the SettingsSelectorPanel, which is still being used in some instances and we aren't ready to fully deprecate, even with a breaking change. So I had to revert those changes, I think at this point we can merge this to fix the original bug. Please assign this to Miles after you've reviewed and then Miles can merge it, since I'm out the next week. |
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.
Main ask is to remove the deleted query params from defaultParams
. But should we also remove query parameters not supported by the mode selector?
"maxBikeDistance": 4828, | ||
"maxBikeTime": 20, | ||
"maxEScooterDistance": 4828, | ||
"maxWalkDistance": 1609, | ||
"maxWalkTime": 15, |
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.
Also remove these deleted parameters from defaultParams
in query.js.
I'm closing the PR, let's try again without all the jank from the revert commits. |
This PR removes a bunch of old query parameters that are no longer needed here, either because they're now directly managed by the mode selector (mode settings) or because they're no longer supported by OTP (like max walk distance).