search

DmitrySharabin / mavo-firebase-firestore

Firebase backend plugin for Mavo. Store and sync app data in milliseconds. Store and serve files at Google scale. Authenticate users simply and securely. All the Google Firebase powers are at your fingertips.
https://plugins.mavo.io/plugin/firebase-firestore
MIT License
6 stars 0 forks source link

mv-path cannot handle multiple layers of nonexistent fields #6

Closed karger closed 4 years ago

karger commented 4 years ago

If you specify mv-path="c" and c does not exist, it is created on save. But if you specify mv-path="c/d" and c does not exist, then the relevant c and d nodes are not created and the save fails silently. Test case here: http://people.csail.mit.edu/karger/Projects/Test/

LeaVerou commented 4 years ago

Are you sure this does not happen with other storage backends? If Dmitry is using the existing Mavo stuff Mavo.Node#inPath IIRC) for handling mv-path, a backend should not be able to break this.

karger commented 4 years ago

You're right, it fails with mv-storage="local" as well.

DmitrySharabin commented 4 years ago

Lea is right; I'm using the existing Mavo stuff.

So I believe I must close this issue since it's not relevant to the plugin itself, and I can't do anything with it.