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
Currently the way this library works requires you to expose your API key in client-side code. The only really secure way around this is to proxy the requests, which implies using a geocoderUrl other than https://api.geoapify.com/v1/geocode/autocomplete
So, it would be nice if the type definitions didn't declare geocoderUrl and placeDetailsUrl as private, or better yet, if there were an option in the constructor / an accessor to modify them.
If there's another solution for protecting the API key let me know!
The text was updated successfully, but these errors were encountered:
Currently the way this library works requires you to expose your API key in client-side code. The only really secure way around this is to proxy the requests, which implies using a
geocoderUrl
other than https://api.geoapify.com/v1/geocode/autocompleteSo, it would be nice if the type definitions didn't declare
geocoderUrl
andplaceDetailsUrl
asprivate
, or better yet, if there were an option in the constructor / an accessor to modify them.If there's another solution for protecting the API key let me know!
The text was updated successfully, but these errors were encountered: