Closed JaseElder closed 3 months ago
I believe the package will eventually support the new API soon or late.
However, I also would like to note here that there are some of us don't want to migrate to new Places API mostly because of the confusing pricing change and missing support for auto-complete query.
The pricing model is quite confusing, but from what I understand, it works out more cost effective, especially if you're using Nearby Search and Text Search. Dropping support for auto-complete sounds crazy though.
Yes it's relatively cost effective for those because it can now define the returning fields from any of the search types, not only "Place Details". However, place autocomplete and query autocomplete seems to be dropped completely:
https://developers.google.com/maps/documentation/places/web-service/op-overview
In other terms, I have to do a Text Search instead of autocomplete, which would cost me 30$ per 1000 search instead of 17$ with autocomplete + details basic info such as place name, address and type.
Hi,
Do you have any plan to migrate to the new Places API?
https://developers.google.com/maps/documentation/places/web-service/migrate-overview