Vehicle Specific Capacities
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 155
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
At the moment we expose a single `vehicleCapacity` property. With it users can set the capacities for _all their vehicles_. What we should do instead is expose a `vehicleCapacities` property (parallel array coinciding with the vehicles) where the user can specify a capacity on a per vehicle basis.
Related: Heterogeneous Fleets https://github.com/mapbox/node-or-tools/issues/11
cc @karenzshea
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing vehicleCapacity API and the related Heterogeneous Fleets issue (#11); no implementation files or tests are named in the payload. Trace how vehicle capacities move through the Node.js bindings into OR-Tools. Done means users can provide a parallel vehicleCapacities array with per-vehicle values, with coverage for the existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100