[Server support] - Update collection-listing strategy from client filesystem #139
Labels
enhancement
New feature or changes to an existing one
P1
Changes that should be worked now
target: collections
Relates to collections, or any of its memos
target: firebase
Relates to Firebase and its sub-dependencies
This issue should solve adding new collections using only Firebase, thus allowing much more flexibility to the client applications when receiving new collection updates.
What it should do, technically speaking, is:
flutter/
tofirebase/
;main
branch) within this new folder of collections, run a script (using Github Actions, through a new workflow) to evaluate such changes, compare this new state to what's stored in the production firestore, and make the required writes to mirror this new state.This is similar to what's occurring locally in
VersionServices
, although there is an additional complexity of handling both global and user collections - meaning that removing/updating past existing user collections should be made with extra care, as to not create any inconsistency.Sub-issue that relates to the Server support - #136.
The text was updated successfully, but these errors were encountered: