-
Notifications
You must be signed in to change notification settings - Fork 3
Feat: add departure time parameter #18
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
Conversation
c2bbac0 to
1ee739a
Compare
julien-nc
left a comment
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.
Which timezone is used by the here API? Since no timezone is specified in the departureTime GET param, it might use UTC.
It would be nice to pass the user timezone (if that is supported by the API) or check if we need to convert the departure time to UTC.
|
If nothing is specified, it's using the local timezone at the origin location what I actually think is quite nice |
|
Yeah, I think that makes sense, no? |
|
Although, if departure_time is None, context agent sends a UTC time, which might be interpreted as local time, if we're departing from, say, Bejing |
|
It adds the timezone in that case so the API knows it's in UTC |
julien-nc
left a comment
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.
👍 🚂
Signed-off-by: Jana Peper <[email protected]>
1ee739a to
1ae36b7
Compare

We can now ask for connections in the future.
The requested time is interpreted in the timezone of the origin ("now" is still now). All time values in the response are returned in the timezone of each location.