You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In mavo when we have mv-app="foo", foo becomes the name by which we can refer to the root object of the app. Which has always been consistent for apps whose root object is an object. But when the root object is a list it got complicated; you need to define a property inside the mv-app to hold the list and change the way you reference it. But now that we have fixed mv-multiple, the consistent way to have an app whose (root) data is a list would just be to put mv-list onto the mv-app element.
In mavo when we have mv-app="foo", foo becomes the name by which we can refer to the root object of the app. Which has always been consistent for apps whose root object is an object. But when the root object is a list it got complicated; you need to define a property inside the mv-app to hold the list and change the way you reference it. But now that we have fixed mv-multiple, the consistent way to have an app whose (root) data is a list would just be to put mv-list onto the mv-app element.
But right now that doesn't work. https://codepen.io/karger/pen/oNmyaqW?editors=1100
The text was updated successfully, but these errors were encountered: