Skip to content
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

Unassigned task type in output #469

Closed
jcoupey opened this issue Mar 18, 2021 · 0 comments · Fixed by #470
Closed

Unassigned task type in output #469

jcoupey opened this issue Mar 18, 2021 · 0 comments · Fixed by #470
Milestone

Comments

@jcoupey
Copy link
Collaborator

jcoupey commented Mar 18, 2021

Currently the unassigned array in output provides an id key matching the input task that we did not manage to fit in. The problem is that we only enforce id values to be unique across same task types (job, pickup or delivery) so in some situations the id information can be ambiguous.

In case of duplicate ids, it's still possible to go through the route steps to see what task types with matching ids are actually included and deduce what is unassigned, but that's definitely not convenient.

We should provide a type key for unassigned tasks, just as for route steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant