Place Autocomplete component/service about google-map

[livtanong]

I think this is already provided for by <google-maps-api>

Usage is

<google-maps-api on-api-load="apiHandler"></google-maps-api>

<script>
Polymer("search-view", {
  apiHandler: function(){
    this.autocomplete = new google.maps.places.AutocompleteService();
  }
})
</script>

[mbykovskyy]

You are right one could implement it themselves and bind it to the input textfield. However, somebody else who needs this feature will have to implement it as well if component isn't generic, which is what this ticket is about.

It was raised as a result of the #41. I was trying to implement google.maps.places.Autocomplete but as @bamnet suggested we need to decide whether to go with a component or a service.

[livtanong]

Ah, makes sense. After all, there's a google-map-search already. I don't think polymer has services, because the whole point is that everything is a component.

[robertrafferty]

I would like to see the Google Places API in a webcomponent.

[ebidel]

Closing as this is pre Polymer 1.0. Please reopen if you can still reproduce or want to see this implemented in the new element.

[gorkamolero]

Yes please! Implement! Implement!

Now a little more seriously:
It is really easy to build an app based on the maps component without resorting to hardcore coding, including heavy shit like markers with custom icons, routes with different travel modes, etc.

However, it's close to impossible to implement a search without going all the way and creating a new component, borrowing from paper elements & behaviors...

The search component should have a UI of its own, including auto complete, in order to be consistent with the easiness of the rest of the components.

Would love to see this.

[kaskaderc]

+1 for making this happen, Can we reopen this FR please?
https://github.com/kunalkundaje/address-autocomplete/blob/master/demo/index.html
shows one way to implement this FR for multiple component addresses.

[ebidel]

I think this is a good idea but we're trying not that take on additional maintenance work for new elements. Does the community one not serve your needs?

[gorkamolero]

It seems like it's one of the few remaining details of the component. Sure, we could do without but it's always going to be way more muddy and convoluted.