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
Thanks for building this field, it have a lot of potential to be used widely!
Still, I think there is an enhancement that will allow the google places api quota (for free usage) not to be exceeded so fast, in case you can use a debounce option.
Meaning, you should only send the request when the user "stops writing in the field after X seconds".
User starts writing the address.
Then he stops writing.
Field waits 5 seconds.
Then makes the HTTP call.
This would reduce drastically the usage of the HTTP requests to the Google places API.
Thanks,
Bruno
The text was updated successfully, but these errors were encountered:
I'll check it out too, and come back as soon as I have feedback. We might need to defer the placechanged event to an intermediate event that will watch the input value being changed.
Hi,
Thanks for building this field, it have a lot of potential to be used widely!
Still, I think there is an enhancement that will allow the google places api quota (for free usage) not to be exceeded so fast, in case you can use a debounce option.
Meaning, you should only send the request when the user "stops writing in the field after X seconds".
User starts writing the address.
Then he stops writing.
Field waits 5 seconds.
Then makes the HTTP call.
This would reduce drastically the usage of the HTTP requests to the Google places API.
Thanks,
Bruno
The text was updated successfully, but these errors were encountered: