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
We're looking to use the Distance Matrix API and come across your wrapper (which looks really useful, thanks!).
The DistanceMatrixRequest has the Origins and Destinations properties that both take an IEnumerable<Location>. The Location class currently has one constructor that takes a lat and long. Would it be possible to take a second constructor where we can pass an address string instead? The documentation indicates that this is an acceptable request.
If you're happy for the change to be implemented I could clone and PR it?
We're looking to use the Distance Matrix API and come across your wrapper
(which looks really useful, thanks!).
The DistanceMatrixRequest has the Origins and Destinations properties
that both take an IEnumerable. The Location class currently has
one constructor that takes a lat and long. Would it be possible to take a
second constructor where we can pass an address string instead? The
documentation indicates that this is an acceptable request.
If you're happy for the change to be implemented I could clone and PR it?
Hi,
We're looking to use the Distance Matrix API and come across your wrapper (which looks really useful, thanks!).
The
DistanceMatrixRequest
has theOrigins
andDestinations
properties that both take anIEnumerable<Location>
. TheLocation
class currently has one constructor that takes a lat and long. Would it be possible to take a second constructor where we can pass an address string instead? The documentation indicates that this is an acceptable request.If you're happy for the change to be implemented I could clone and PR it?
Thanks,
Lee & @Dingwall
The text was updated successfully, but these errors were encountered: