Dmitry Sharabin

> Can we make a testcase that doesn't depend on async expressions, which are a rather new feature? > You could make a backend stub (the backend tests have some...

As for me, I would stick to the first variant: the code looks much more like native HTML, and if an author decides to integrate Mavo with other third-party libraries...

Suddenly I came up with this: ``. I suppose, in that case, we won't have to invent special symbols for “gaps” and a new syntax for destructuring, and we won't...

Do we really need `mv-group` here? `` It causes the weird output you mention in your pen: `m2: { "m2": [ "" ], "x": 3, "y": 4 }`.

@karger Actually, it's not an issue with Mavo, but with the Firebase Firestore plugin. Precisely, with its _offline persistence_ feature which is enabled by default. Once, we discussed this feature...

I looked through the Cloud Firestore documentation one more time and watched their tutorials, and here are some excerpts and my thoughts: - For the web, offline persistence is disabled...

> I don't recall the discussion for moving to mv-storage-options. the new syntax seems less general in that it doesn't suggest a consistent way to provide options to plugins that...

What do you think of using `` as such an element? We already use an attribute with the same name, so, to my mind, it's natural to stick to it...

> Always think of example code when proposing names or syntaxes. My bad. Sorry. I was thinking of something like: `` or `bar` >What about ? I'm OK with this...

As we know, backends that support authentication provide the `user` object to Mavo, and Mavo uses it to add some info about a logged-in user to the Mavo bar. We...