You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The determination of the day on which an itinerary with transit happens is currently done using the itinerary start/arrive time and the SERVICE_DAY_START_HOUR config param. This approach is redundant with the serviceDate field on itinerary legs for itineraries returned by OTP.
Observed behavior
The determination of the day on which an itinerary with transit happens is currently done using the itinerary start/arrive time and the
SERVICE_DAY_START_HOUR
config param. This approach is redundant with theserviceDate
field on itinerary legs for itineraries returned by OTP.This issue is related to opentripplanner/otp-react-redux#385 and opentripplanner/otp-react-redux#372.
Expected behavior
The determination of the day on which an itinerary with transit happens should use the
serviceDate
field returned by OTP.Steps to reproduce the problem
NA
Any special notes on configuration used
NA
Version of otp-middleware and/or OpenTripPlanner if applicable (exact commit hash or branch name)
recent code on the
dev
branch.The text was updated successfully, but these errors were encountered: