Thomas Bouldin

BTW, I'm trying to catch examples of sub-optimal Promise usage in the wild and wanted to point out the one in this thread, CC @Sun3 Promise code should almost never...

Yes, the client SDK works in Node. We actually use the Client SDK in Node as part of `firebase-tools`, so this is pretty unlikely to change any time soon.

Internal feature request number 235998431

Both features have been submitted for API review, which is a formal step before any implementation can begin. One thing I realized during my research though is that autogenerated document...

Indeed. That code is for truly unique IDs. I thought Firestore was like the Realtime Database, which uses base64 encoded timestamps along with an anti-collision nonce.

This feature has been formally proposed internally.

We're currently in the early phases of rearchitecting our emulator to be a better foundation for the future and any investment we make at the moment into hot-reloading would need...

@SrBrahma Your use case is interesting but should be unaffected by this. CCing @taeold for thoughts on how to allow customers to provide (real) secret values without serializing to the...

This will be part of Cloud Functions for Firebase v2 GA but is not a blocker for public preview. We are considering multiple avenues, including build env files.

@elhe26 For non-sensitive params we back everything in dotenv files. For secret params we use CSM exclusively as our backing store at this time.