The client's Firestore data serves reads from and pushes writes to different interfaces. In staging and prod this is not a problem because the read-only data service is eventually consistent with respect to Firestore (which we use as a write service).
In testing and dev though, there is currently no mechanism that prevents authenticating against and then writing to Firestore. This can confusion in the UI and unintended writes.
On
firebase-and-serverbranch:The client's Firestore data serves reads from and pushes writes to different interfaces. In staging and prod this is not a problem because the read-only data service is eventually consistent with respect to Firestore (which we use as a write service).
In testing and dev though, there is currently no mechanism that prevents authenticating against and then writing to Firestore. This can confusion in the UI and unintended writes.