Fix distance and duration values, basic support for proxy and additional HTTP headers #93
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently distance and duration is not parsed and translated correctly. For example the distance
distanceValue
anddurationValue
are not correct and cannot be used as such. They do not include the distance and duration from all thelegs
.I have introduced these values for the
PolylineResult
that is reflected in thelegs
;I have taken the liberty to not include tests as we basically use
reduce
to infer values directly from Google.