Add allowOverloading parameter to GBFS updaters and fix use of it in routing - #5024
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## dev-2.x #5024 +/- ##
=============================================
+ Coverage 64.25% 64.28% +0.02%
- Complexity 13786 13791 +5
=============================================
Files 1689 1689
Lines 66773 66778 +5
Branches 7191 7191
=============================================
+ Hits 42906 42925 +19
+ Misses 21461 21450 -11
+ Partials 2406 2403 -3
... and 2 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
| ) | ||
| implements VehicleRentalDataSourceParameters { | ||
| public boolean isAllowOverloading() { | ||
| return allowOverloading; |
There was a problem hiding this comment.
???
Can you not just call allowOverloading()?
|
I think I've implemented everything we discussed in the dev meeting. Only thing I'm still unsure about is what to do with the allowOverloading in the GraphQL schema. I don't know if anyone is actually using it so we could maybe just rename it to be overloadingAllowed? |
| import org.opentripplanner.street.search.state.State; | ||
| import org.opentripplanner.transit.model.framework.FeedScopedId; | ||
|
|
||
| class VehicleRentalEdgeTest extends GraphRoutingTest { |
There was a problem hiding this comment.
| class VehicleRentalEdgeTest extends GraphRoutingTest { | |
| class VehicleRentalEdgeTest { |
Do you need the GraphRoutingTest?
There was a problem hiding this comment.
Well spotted. Seems like it's not needed. I used another test class as the basis for mine but it was unnecessary in the other class as well so I removed it from both.
|
Please resolve the conflicts. |
Summary
This adds optional
allowOverloadingparameter to the GBFS updaters and fixes use of it in routing.Issue
This is related to MobilityData/gbfs#376 but unfortunately currently, I don't feel like there is a straightforward way to define this information in the data.
Unit tests
Updated tests.
Documentation
Updated
Changelog
From title