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
What do you guys think - would it make sense to integrate node-geocoder to e.g. easily get products by address? I think most people will use it anyways to get lat & lon values for the calls...
- added all methods for #24 including tests
- updated READMEs & example files
- reworked entire testing architecture for #41
- removed deprecated methods for #42
- added scope checks for #40
What do you guys think - would it make sense to integrate node-geocoder to e.g. easily get products by address? I think most people will use it anyways to get lat & lon values for the calls...
I'd propose adding 3 new methods, e.g.:
uber.products.getAllForAddress(address)
uber.estimates.getPriceForRouteByAddress(start_address, end_address, [, seats])
uber.estimates.getETAForAddress(address [, product_id])
In addition to that, some methods might need to be revisited:
uber.requests.create(parameter)
uber.requests.getEstimates(parameter)
uber.requests.updateByID(request_id, parameter)
uber.reminders.create(parameter)
uber.reminders.updateByID(reminder_id, parameter)
.The text was updated successfully, but these errors were encountered: