In the following screenshot documentation is using a small value for minimumFetchIntervalMillis without specifying that.

I have expected the value to be the default production value, or to at least have a comment that this value is a development specific value.
Reading the followin

What feature would you like to see?

Firestore has DocumentReference.addSnapshotListener and [Query.addSnapshotListener](https://firebase.google.com/docs/reference/androi

For Firestore collections and docs, it would be nice if each of the ...Data hooks would automatically add the idField (if provided) as a key/value to the <T> generic.

For example, the useDocumentData hook would return something like T & { idField: string } instead of just T. In this case, idField should be represented by the actual string value entered into options.idField.

D

Firebase has the ability to set a language code so that password reset emails show up in the set language.

https://firebase.google.com/docs/auth/web/manage-users

firebase.auth().languageCode = 'fr';

Should read "Calls OnSetSuccess on success", but currently reads "Calls OnUpdateSuccess on success". Also reads "Calls OnUpdateFailed" rather than "Calls OnSetFailed".

Super easy to fix and is pretty annoying until a hypothetical dev decides to start trying random event handlers in desperation ;)

Specifically, line 467 and 468 of file

https://github.com/dkrprasetya/simple-firebase-unity/

https://stackoverflow.com/questions/55423486/is-it-reliable-to-use-email-address-as-primary-key-uid-on-firebase-realtime-data?noredirect=1#comment97566454_55423486

Imagine this:

User 1 email address = johndoe@foobar.com
User 1 escaped email address = johndoefoobarcom

User 2 email address = jo.h.ndo.e@foobar.com
User 2 escaped email address = johndoefoobarcom