Closed EECOLOR closed 5 years ago
@LoveMHz
Great question!
I do not think this library can support Firestore. There are a few reasons:
Another thing that might be problematic is that we are not using Firestore in any of our projects. This would have a negative effect if we had Firestore support in this project:
So I think the best thing would be a separate project with maintainers that know how Firestore works. I would suggest to use the same surface API and behavior (as far as possible) as this library. This would benefit end-users (developers) and allows them to switch their application to another store. If it helps feel free to fork this library and convert it into a Firestore version!
Ohw, I forgot to add: please let me know if you disagree, I try to be open for discussion.
It is also possible to use both Realtime DB and Firestore DB in the same project. So the one solution might be to keep parts of your app separated, logic for queuing could use RealtimeDB and the rest of your app could use Firestore DB.
I'm closing this issue. If anyone feels it needs to be reopened, please feel free and don't forget to add a motivation and counter arguments.
https://github.com/kaliberjs/firebase-queue/issues/5#issuecomment-419212802
@LoveMHz: