v0.3.6

• Updated Firebase version
• Adopted the backend metadata API
• Minor improvements

v0.3.5

Release 0.3.5

v0.3.4

Introduces crucial improvement—fixes the issue with data serialization.

Also, a couple of minor improvements.

v0.3.3

Minor improvements.

Dependencies for plugins that are out of the plugins repo should be appropriately specified—they must have absolute addresses (URLs), not relative ones. In the dev version of Mavo relative addresses work fine, but to make a plugin compatible with the previous versions of Mavo, plugins authors should use URLs.

v0.3.2

Bug fixes and minor improvements.

v0.3.1

Introduce rather minor improvements.

Since the plugin gets mature, I need to fix its state to continue working on Firebase specific features: change the way to store an app's data (use all the Firebase powers—built-in collections and files), incremental savings, and finally granular permissions.

These will be the breaking changes, and we must introduce them to let Mavo be more awesome. 🤩

v0.3.0

Add authentication with Firebase using Google, Facebook, Twitter, or GitHub accounts

v0.2.2

Bug fixes and general improvements.

v0.2.1

Add the firebase:// ”protocol URL”.

Credit to David Karger.

v0.2.0

1. We don't need databaseURL anymore—it's sufficient to know projectId so we can get and construct everything we need out of it. projectId is one of the parameters we get when registering our Firebase web-app.

2. To enable the plugin, as the mv-storage value we'll be using projectId. E.g., mv-storage="mavo-demos".
   Note: This release is backward compatible, so we can still use databaseURL as an mv-storage value.

3. By default, the Firebase backend stores data in the mavo-apps collection in a file whose name matches the name of a Mavo app. We can change it by specifying the name of the collection (and a path to it) and the name of the corresponding file after the projectId. The projectId, the collection name, and the filename must be divided by forward slash, like so: mv-storage="projectId/path/to/collection/filename". We can also leave the default filename and specify only the collection, like so: mv-storage="projectId/path/to/collection".
   Note: For now, there is no way to specify only the filename without specifying the collection. The only way to do that is to provide the full path, with the collection name (including the default one).