Changed to use Google Places API

I'm hoping to create a PR around the switch or option to use "google places api" rather than "geocoder". Is that something still of interest?

The main thing I need is to be able have results biased to the users current location, which "google places api" supports.

If I resolve the merge conflicts on this, is this something that can be merged into master?

Mar 09 '15 22:03 kevbaker

Yup, definitely :)

Mar 09 '15 22:03 etodanik

@kevbaker how is it going with resolving conflicts?

May 29 '15 01:05 okonon

I have this all completed with a few extra updates from HEAD.

I'll create a new PR so it can be merged.

On Thursday, May 28, 2015, softBarbarian [email protected] wrote:

@kevbaker https://github.com/kevbaker how is it going with resolving conflicts?

— Reply to this email directly or view it on GitHub https://github.com/israelidanny/ion-google-place/pull/5#issuecomment-106647217 .

May 29 '15 14:05 kevbaker

So what's the story with this?

Jul 25 '16 00:07 goneale

I'm going to look into the option of allowing flexibility between using google places api or geocoder. There are use cases for both.

Jul 25 '16 15:07 etodanik

Hello, we have this setup. It works great. I'll talk to our developer. I had thought he sent a PR On Mon, Jul 25, 2016 at 8:02 AM Danny Povolotski [email protected] wrote:

I'm going to look into the option of allowing flexibility between using google places api or geocoder. There are use cases for both.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/israelidanny/ion-google-place/pull/5#issuecomment-234979512, or mute the thread https://github.com/notifications/unsubscribe-auth/AACpvm2m_9zfP0CQ5Rfk-R7elLOXbWeBks5qZM-_gaJpZM4CxF9K .

Jul 25 '16 15:07 kevbaker