epodol
epodol
@prc5 Can we please merge this?
From what I understand about preloading the Firestore SDKs, when preloading Firestore, all you are doing is preemptively importing Firestore once, higher in the component tree, and suspending the application...
Glad that helped @dylangarcia! Here are two more things you can try to make it work a bit better (similar to what you just mentioned): - Add another `` directly...
@jhuleatt If you would like, you can assign this to me. I would be happy to implement this. I was thinking this could be an option like: `allowNullReference`. This would...
> Hey @ky28059 and @epodol, this request has come up a couple of times ([#178 (comment)](https://github.com/FirebaseExtended/reactfire/issues/178#issuecomment-550503600), [#166 (comment)](https://github.com/FirebaseExtended/reactfire/issues/166#issuecomment-544642338)). > > My opinion is that this would create an opportunity for...
This is probably also related. ```typescript const { status: useInitFirestoreStatus, data: firestore } = useInitFirestore( async (firebaseApp) => { const firestoreInit = getFirestore(firebaseApp); if (isDev) connectFirestoreEmulator(firestoreInit, 'localhost', 8080); return firestoreInit;...
It looks like the code is being run after every other useInit... completes.
Yes, this still occurs with `initializeFirestore`. With a console.log inside the callback, it gets called once for each of the init callbacks defined.
Correction, my prior problem has been resolved by adding `{ suspense: false }` to each of the useInit calls. However, when enabling offline persistence, I get a similar effect to...
> Interesting, thanks for the follow up @epodol. Having to add `{ suspense: false }` to each call sounds like a bug (the `useInit` hooks should pick that up from...