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.

Sign up for GitHub

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

Jump to bottom

Questions and fixes on TripCoverage #406

Closed

ralfbayer-db opened this issue Dec 6, 2023 · 1 comment · Fixed by #429

Assignees

Labels

Milestone

Collaborator

ralfbayer-db commented Dec 6, 2023

Description of "TripCoverage": If neither leg ids nor section ids are not defined, the complete trip is covered. The "not" ist wrong.
Can both "coveredLegIds" and "coveredSections" be filled? Does this make sense? It should be stated that they are mutually exclusive.
What is the exact semantics of "coveredSections"?

ralfbayer-db added the documentation label

ralfbayer-db added this to the 3.2.0 milestone

ralfbayer-db self-assigned this

Collaborator Author

ralfbayer-db commented Jan 5, 2024

patch the documentation.
coveredLegs and coveredSections are mutually exclusive.
ralf to provide a patch for next week.

ralfbayer-db linked a pull request

that will close this issue

Improve documentation of TripCoverage #429

Merged

jspetrak closed this as completed in #429

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