-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Avoid NullPointerException in GTFS GraphQL API #6274
Avoid NullPointerException in GTFS GraphQL API #6274
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev-2.x #6274 +/- ##
=============================================
+ Coverage 69.74% 69.75% +0.01%
- Complexity 17732 17742 +10
=============================================
Files 2010 2010
Lines 75923 75925 +2
Branches 7776 7776
=============================================
+ Hits 52951 52962 +11
+ Misses 20261 20255 -6
+ Partials 2711 2708 -3 ☔ View full report in Codecov by Sentry. |
Why do you say that only flex legs can have a booking info? It is recommended as long as a stop has pickup_type or drop_off_type as call agency, and this applies to scheduled service (e.g. coach services) as well. |
In the GTFS spec you can put them anywhere but OTP only adds them to Flex legs. We can of course change that. |
Summary
It fixes a NPE in
BookingInfoImpl
whenminimumBookingNotice
is null.Issue
Closes #6273
Unit tests
Added. The reason that I didn't add a new file to
GraphQLIntegrationTest
is that only flex legs can currently have a booking info, which would require me to add a flex leg and update all assertion files.