Question: Is this Directive uses Session tokens ? about ngx-google-places-autocomplete HOT 6 CLOSED

I was using this directive and my client was being billed $$$$$ since every keystroke is billed. I had to ditch this directive and write my own service that utilizes AutocompleteService. If you plan to go that route, I would also suggest using "offset". The "offset" property tells the service to start making API calls after n number of characters have been typed. Using AutocompleteService gives you more control over when to make an API call. You also write code to display the list of returned addresses.

from ngx-google-places-autocomplete.

Attention needed to this issue.

from ngx-google-places-autocomplete.

I guess there's a lot of work to do about this, because:

1. You have to replace Autocomplete with AutocompleteService
2. You have to listen to keypress/keyup/keydown event from native element in order to call the AutocompleteService
3. Build a function to show the results, hoping the one provided by Google example is correctly working. As I see online it seems it's not built to provide a "suggestion" system for inputs, because you need to create the whole "popup" under the input, manage clicks and so on
4. Provide the token to use it in the placeDetail() request

from ngx-google-places-autocomplete.

Thank you Imran, I hate the fact that you have to write your own callback to render the results. Why tf Google doesn't implement token for Autocomplete I really don't know

from ngx-google-places-autocomplete.

As far as that library is just a wrapper for google places autocomplete, it doesn`t use session tokens.
But you should be able to use fields property for customization #36

from ngx-google-places-autocomplete.

According to this: https://developers.google.com/maps/documentation/javascript/places-autocomplete#session_tokens session tokens are automatically handled by the widget. So in that case this directive is using session tokens.

from ngx-google-places-autocomplete.