Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Geosuggest is unable to catch google api error
See original GitHub issueShort description
I was trying to create UI which will rendered differently if geosugget input has an google api error.
Expected results
I expected that should be a call back function such as onGoogleAPIError, so I will know there is an api issue and then render my ui accordingly.
Actual results
There is no way to know if google api call is failed.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Error Messages | Maps JavaScript API
If you encounter an error while loading the Maps JavaScript API, please see the table below to find explanations for the error codes....
Read more >Bare minimum google places api fields to have react- ...
The Places Details service must be called in order to get information about the selected place from Autocomplete suggestions.
Read more >react-geosuggest
A React autosuggest for the Google Maps Places API.. Latest version: 2.14.1, last published: 2 years ago. Start using react-geosuggest in ...
Read more >react-geosuggest | Yarn - Package Manager
Live demo: ubilabs.github.io/react-geosuggest. Installation. As this component uses the Google Maps Places API to get suggests, you must include the Google ...
Read more >react-geosuggest/CHANGELOG.md
The CDN for react-geosuggest. ... 420, * "use strict"; no longer throws errors if google cannot be loaded ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That could be nice to have. If you want a feature like that, feel free to implement! A unified onApiError handler would be nice I think. We use three APIs and there should be at most 1 handler I think.
What do you think?
@ro-ka sure will do.