You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
what about Firestore transactions, batched writes, field value operations (e.g. FieldValue.arrayUnion)?
Long version
First off, thank for this repo! I have been developing apps in Flutter and it is refreshing to see a different take on app architecture. I have learnt a lot from your work.
I am considering the abstraction you use for working with Firestore db. The approach of viewing it as a CRUD db makes testing easier and also probably migrating to a different db possible.
This abstraction, however, comes at the cost of not having access to the Firestore's advanced features such as transactions, batched writes, field operations such as FieldValue.arrayUnion(), FieldValue.increment(), etc.
I'm interested to know how would you approach exposing these features while still aiming for testability and portability.
The text was updated successfully, but these errors were encountered:
TL;DR
what about Firestore transactions, batched writes, field value operations (e.g.
FieldValue.arrayUnion
)?Long version
First off, thank for this repo! I have been developing apps in Flutter and it is refreshing to see a different take on app architecture. I have learnt a lot from your work.
I am considering the abstraction you use for working with Firestore db. The approach of viewing it as a CRUD db makes testing easier and also probably migrating to a different db possible.
This abstraction, however, comes at the cost of not having access to the Firestore's advanced features such as transactions, batched writes, field operations such as
FieldValue.arrayUnion()
,FieldValue.increment()
, etc.I'm interested to know how would you approach exposing these features while still aiming for testability and portability.
The text was updated successfully, but these errors were encountered: