Martin Schuhfuss
Martin Schuhfuss
Try it like this: ```tsx const AppCheckHandler = () => { const coreLib = useMapsLibrary('core'); useEffect(() => { if(!coreLib) return; const settings = coreLib.Settings.getInstance(); settings.fetchAppCheckToken = async () => {...
AppCheck is likely going to gain usage over time, so it would still make sense to add it to the APIProviderProps or add a hook to make it easy to...
@fredrikj31 I'm not sure what the ergonomics should be like. How would you prefer having this handled? Some Ideas: ### Handled by APIProvider ```tsx import { initializeAppCheck } from 'firebase/app-check';...
That is interesting – maybe I misunderstood how this actually works. The way I understood it was that we can't rely on the token being a single stable value for...
And in your case, you could put that function neatly away into your `FirebaseProvider` and expose it via a hook `const fetchToken = useAppCheckToken();` where the APIProvider is created.
Not sure I'm understanding what you are asking for. We do publish the `./dist` folder with all releases (see https://www.npmjs.com/package/@googlemaps/markerclusterer?activeTab=code). Or where did you expect to find them?
Thanks for clarifying. Those are snapshots of the GitHub repo for the release-tags, and as such don't contain the generated files. I'm not sure if it's possible to replace them...
Thanks! The official documentation doesn't have any information on why the types for `map.center` etc are specified as "might be undefined" and in about ten years with the maps API,...
I'm not an expert on CSP issues, but I think this could help: https://developers.google.com/maps/documentation/javascript/content-security-policy Note that we will reuse the nonce-value of the first script-tag that has one: https://github.com/visgl/react-google-maps/blob/40b47d4894cfbea1edfc627513f7713db499eea5/src/libraries/google-maps-api-loader.ts#L149-L151 Maybe...
Just noticed the part about this being in a chrome extension. I think I read somewhere that external scripts will no longer be supported in chrome extensions as of manifest...