-
Notifications
You must be signed in to change notification settings - Fork 126
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
[Jormungandr] Implement pt journey fare #4089
Conversation
6b84f85
to
503c707
Compare
0bbb49b
to
00f9d42
Compare
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.
After discussion, the assumed behavior for this feature is gonna be:
"trigger (or not) a fare-computation, no matter if it was already computed".
Which means that the trigger-fare and pt-journey planner params will have to be maintained/used at the same time.
So it may lead to (bold are "weird" but assumed):
- double fares in result (case of Kraken journey + trigger)
- single fares in result (case of Loki journey + trigger, or Kraken + no-trigger)
- no fares in result (case of Loki journey + no-trigger).
This explains:
source/jormungandr/jormungandr/pt_journey_fare/pt_journey_fare.py
Outdated
Show resolved
Hide resolved
source/jormungandr/jormungandr/pt_journey_fare/pt_journey_fare.py
Outdated
Show resolved
Hide resolved
e60378f
to
22902c1
Compare
Kudos, SonarCloud Quality Gate passed! |
No description provided.