v0.4.2

Bump the version up to tag a new release and purge the JSDelivr cache

v0.4.1

It's a minor release where we fixed a long-standing bug with the login button inside the Mavo bar. You might never face this issue unless you have more than one app on the page using the plugin.

v0.4.0

It's been a long time since the last release, and we genuinely believe this one is worth all the waiting.

• Starting from this release, the plugin allows you to work with a collection of documents in addition to working with a single document. 🥳 Not only that, you can also perform queries to get only those documents you need, thanks to the new mv-storage-query attribute. See the docs for more information.
• We updated the Firebase library the plugin uses. So, under the hood, the plugin has the greatest and latest Firebase features.
• It is worth also noted that with this release, we introduced a breaking change: previously deprecated attributes mv-firebase-key, mv-firebase-auth, mv-firebase, and mv-firebase-storage are now removed. Use mv-storage-key, mv-storage-providers, mv-storage-options, and mv-storage-bucketname storage attributes instead.
• We fixed a bunch of bugs that caused the plugin to work unexpectedly in some cases.

Huge thanks to @karger for pushing the plugin evolution!

v0.3.13

Some patches. Special thanks to @karger for finding bugs.

v0.3.12

Bug fixes.

v0.3.11

Add a quick (undocumented) escape hatch for skipping the warning about unsaved data when real-time updates are enabled—the skip-unsaved-data-warning option.

v0.3.10

This is a rather minor release.

• We got the plugin ready for the new Mavo version by adopting some upcoming APIs.
• At the same time, we kept it supporting Mavo prior to v0.2.4.
• If the realtime feature is enabled, we ask an end-user for confirmation whether to accept the pushed data changes or not if there are unsaved data.

v0.3.9

Add warnings about deprecated attributes. No new features.

v0.3.8

Make offline persistence optional. From now on, it's not enabled by default anymore. An author must enable it explicitly in case they need this feature.

Details

The plugin supports offline data persistence. This feature caches a copy of the data that your app is using, so your app can access the data when the device is offline. When the device comes back online, the plugin synchronizes any local changes made by your app to the backend. To enable this feature add offline-persistence option to mv-storage-options.

Note: Please keep in mind that if you enable both the realtime and the offline persistence features simultaneously (i.e., you specify mv-storage-options="realtime offline-persistence" in the root of your app), that might cause some issues with realtime updates if your app is opened in more than one tab. Changes made in the app in one tab won't be pushed to the app in the inactive tab.

v0.3.7

Fix issue when Firebase is not primary backend but still determines whether the Login button is shown or not. See mavoweb/mavo#668. That was not a Mavo bug but the plugin.