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
{{ message }}
This repository was archived by the owner on Apr 19, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 19, 2026. It is now read-only.
How to prevent OVER_QUERY_LIMIT with google-map-search and input #387
It kind of works: the map updates the markers based on the results from the input typed in the paper-input element.
However, if I type too fast, I noticed the error on the console: Cannot read property 'map' of null
After a while I found out it's returning OVER_QUERY_LIMIT status from Places Service. Is there a correct way to prevent this? Thanks!
Hello.
I'm trying Polymer for the first time and developing a simple view like so:
<paper-input value="{{input}}"></paper-input><google-map-search map="{{map}}" query="{{input}}" results="{{results}}"></google-map-search> .....It kind of works: the map updates the markers based on the results from the input typed in the paper-input element.
However, if I type too fast, I noticed the error on the console:
Cannot read property 'map' of nullAfter a while I found out it's returning OVER_QUERY_LIMIT status from Places Service. Is there a correct way to prevent this? Thanks!