Michael "Tres" Brenan

Dataview tracks both the original name for every field, as well as a canonicalized name, mainly so that multiword fields can be accessed more easily from Dataview/DataviewJS, and because people...

I've added that, and general UX improvements, on my todo list right after I do some more bug hunting and query usability improvements.

I'll have to see if I can hook into the existing renamer to also do codeblocks; as far as I'm aware, Obsidian intentionally skips frontmatter and codeblocks by default.

I'm still fiddling with some performance things, but Dataview does have a full markdown parser implementation now (that's just not hooked up to the indexer): https://github.com/blacksmithgu/obsidian-dataview/blob/master/src/data/parse/markdown.ts. We can afford to...

Sort the rows in the desired order before grouping - they should then be sorted correctly.

When you use `GROUP BY`, it is changing how the data looks - your query then operates on groups and not on individual pages. So if you `GROUP BY .....

Sorting before a group should sort values inside the `GROUP BY`; sorting after a group sorts the groups.

I think this may be a bug on my part. Let me check.

Bad link parser implementation; thanks for flagging.

The rendering issue appears to be Obsidian - I get it even for basic escaped links like `[[Hello\|There]]` (which still renders a "There" in Obsidian). Also, now that I looked...