firetable VS testing-cloud-firestore

I love using Firestore & cloud functions, for their simplicity. However, as your product becomes more complex, building cloud functions turn into real struggles - especially when you have so many Firestore document level triggered events to deal with.There are only two options currently and neither of them ideal: 1. Make a big cloud functions that do multiple things - gets quite messy 2. Deploy multiple cloud functions that listen to the same trigger - you end up having to add add boilerplate code to filter out the field changes On top of that, as the projects get bigger, ran into other issues like:- Tons of dependencies to manage- Slow functions as unwanted dependencies are installed- Cold start problem to configuretoo messy and the issues start to snowball….. With Firetable, an open-source project that allows you to manage data in Firestore with a spreadsheet like UI and unlock many of the functionality of GCP like building cloud functions on Firestore data triggers at field level, we try to make this process super simple, visual and intuitive. We have been working on it for past two years and recently this week released a new version with exciting features including:- Ability to write functions that evaluate only when specific fields are set or updated- Using cloud run instance to build and deploy functions by installing only the dependences that are actually being used We would love to get your feedback on this feature or firetable in general, check it out using the links below: Github repo: https://github.com/FiretableProject/firetable Demo video: https://www.youtube.com/watch?v=0IQbFyFvjDg Chat with us on Discord: https://discord.gg/B8yAD5PDX4

to learn more about firetable you can checkout the github repo : https://github.com/FiretableProject/firetable

If you're looking for guidance on the implementation you can take look at the Firetable implementation of this feature here

I’m a software engineer building Firetable, an open-source React app that combines a spreadsheet UI with Firestore and Firebase’s full power. We ran into this exact issue with some fundamental code: the code for all the different field types, from the simple ShortText to the complex ConnectTable field.

That cleanup you mentioned is pretty much what I'm doing here: https://github.com/danahartweg/testing-cloud-firestore/blob/master/server/test-helpers/firestore-helpers.ts#L65 ... I can't say I've encountered the warnings you saw, but my gut says they're related to parallel execution.