mavo
mavo copied to clipboard
mavoweb
Properties on Lists?
Splitting mv-list and mv-list-item creates a new opportunity---or a new opportunity for messing up. It is now possible to define a property inside the mv-list but outside the mv-list-item. Mavo does not currently handle this well. https://codepen.io/pen?template=gxPjmz&editors=1100#0 . I think it completely ignores the property definition. There certainly doesn't seem to be a way to access it.
But actually, as in js, it is theoretically reasonable to have a list that also has other properties than the list-item 1...n properties. Do we want to support this in mavo. or will it make our novice programmers' heads hurt? If not, perhaps there should be an exception thrown if someone defines a property in this wrong place.
https://codepen.io/pen?template=gxPjmz&editors=1100#0.
@karger It looks like you copied the Codepen URL before saving it, so it's broken. Could you please update it?
The downside is that this does not translate to JSON, so we lose the ability to represent any Mavo data model with JSON. We could of course use some kind of convention to represent these, but it's more clumsy. But we generally don't add functionality because it seems cool, do we have use cases for this?
Looks like I never saved it, so here is a new one https://codepen.io/karger/pen/Yzgwjbz?editors=1100 . I think I discovered this by accidentally putting a property in the wrong place. Even if we don't support it we should handle it properly. E.g. report an error.