-
Notifications
You must be signed in to change notification settings - Fork 543
Description
When we set up firetable for a Firebase project and create a table, we start seeing metadata collections (e.g. _FIRETABLE_, _FT_USERS) created in the top level of Firestore. These metadata are mixed up with existing data generated by the users of the app
-
Is there a way to group the metadata up (e.g. Firetable/firetable/___)?, so then all the metadata along with the data entered through the Firetable CMS is organized into one spot.
-
If the answer is no for 1), then for separation of concern, do you recommend creating a separate Firestore instance (i.e. separate Firebase project as Firebase doesn't support more than one firestore instances right now) for data entered through the Firetable CMS?
-
any other suggestions in separating the data generated by Firetable CMS and data generated by users through the app?