Michael "Tres" Brenan

Dataview headers are not "real" headers and can't be linked to (since they directly render to your view, and are not Markdown).

As a more philosophical question, why use the inline keys over YAML frontmatter? YAML probably is the most terse way to describe nested objects.

That query should return your mentioned task; A task is only considered completed if it is explicitly 'x' or 'X'. It may be another part of the query excluding it.

This errors appears to be happening inside the minified code for one of the libraries, for some reason. Additionally, apparently the `itemsAray` actually affects whether or not this crashes, which...

Well, this is tremendously annoying. The issue is your loop - it should be ```js for (var i=0; i < items.length; i++) ``` instead of ```js for (i=0; i <...

Doing `i=0` is overriding an esoteric, minified `i` variable inside some minified library code; this is because the global state is still implicitly available in the eval'd script (which I...

Yeah, a very valid workaround is to jkust make sure to use `let`/`var`/`const` in your variable definitions - I'll see what I can do about improving the error UX.

I think there are two main points: - More easily include child elements in task-y queries. It is a little annoying right now, which is something I have been thinking...

Dataview is interpreting the codeblock starting with `============================...` as an inline dataview query and attempting to evaluate it. I suspect you would see the dataview errors in Read mode, or...

Are these defined in frontmatter? If so, Dataview swapped to the Obsidian standard for frontmatter links, which is to define them as ``` parent: "[[Link]]" ``` instead of ``` parent:...