thdk / firestorable Goto Github PK

in case of just one id=> simply update the document.
otherwise, use a batch (max 500 docs), to update all documents with given ids.

Currently no cache is set up.

We can set up cache for:

• install npm
• install firebase-tools
• setup firestore emulators

See emulator-suite/install_and_configure for note regarding caching the emulator files.

https://firebase.google.com/docs/emulator-suite/install_and_configure#integrate_with_your_ci_system

For inspiration: https://github.com/reduxjs/redux/blob/master/rollup.config.js

Whenever a commit with tag v.* is pushed on master branch, it should automatically start tests and deploy new version on npm.

https://circleci.com/blog/publishing-npm-packages-using-circleci-2-0/

The mobx methods 'onBecomeObserved' and 'onBecomeUnobserved' for the docs property of the Collection class can be useful for detecting when listener for realtime database changes should be activated or deacativated.

https://mobx.js.org/refguide/api.html#onbecomeobserved-and-onbecomeunobserved

Assigning null to the query of a collection means you want to return zero documents for that collection.

Example when no user is logged in, you can assign null to the query of a collection to clear the current docs.

Problem: when a collection is not being observed and the query is set to null, there is an early exit happening before the documents are cleared. In that case the document will not have been cleared.

Currently the generated bundle is es6. We need to both es6 and commonjs bundle.

in package.json
... 'main' points to CommonJS and the 'module/jsmain:next' field(s) point to ESM. Thus having one package with proper support for Node and package bundlers.