Open karger opened 4 years ago
The problem is that mv-path
is a node attribute, not a Mavo root attribute. It can be specified on any property. But I can see these attributes as special cases for the root. #536 should also address this. If we implement #536, then it's questionable whether the use cases for this are sufficient to warrant special declarative syntax.
If you're fetching data from one place and writing to another, it seems questionable to assume that the data you want to work with is on the same path in both location. perhaps mv-source-path and mv-storage path could be used (with shorthand mv-path for both).