'[]()' rendered as link in dv.pages() folder query, but string in #tag query

Describe the bug I’ve been trying to remap fields to create a new list of markdown links (i.e. [file.alias](file.path)), and discovered that using identical queries with dv.pages() creates different results depending on whether you’re querying a folder or a tag.

To Reproduce

1. Create two dataviewjs blocks like this: console.log(dv.pages("#project").map(k => '[' + k.file.name + '](' + k.file.path + ')')) console.log(dv.pages('"Folder"').map(k => '[' + k.file.name + '](' + k.file.path + ')'))
2. If you check the output, you’ll see each creates an array with identically formatted items: "[name](path)"
3. Now use dv.list() instead of logging to the console dv.list(dv.pages("#project").map(k => '[' + k.file.name + '](' + k.file.path + ')')) dv.list(dv.pages('"Folder"').map(k => '[' + k.file.name + '](' + k.file.path + ')'))
4. You should see something like this:

In other words, a folder query actually renders the markdown, while a tag query simply displays the plaintext.

Expected behavior Instead, I’d expect each of these to be rendered the same, with working links to the notes. The source should have no effect on the way it’s rendered, no?

Desktop (please complete the following information):

• OS: MacOS Big Sur
• Obsidian Version [e.g. 0.12.13]
• Dataview Version [e.g. 0.4.4]

[blacksmithgu]

@nkoder I did some investigation and I think you are exactly correct. Obsidian does not like spaces in paths to markdown files, and will not render them as links unless you replace space with %20.

As another option for this, note there is a link method withDisplay which lets you set the render for the link. Try this:

dv.list(dv.pages("#thing").map(k => k.file.link.withDisplay(k.file.aliases[0] || k.file.name)));

[blacksmithgu]

Good to hear you found a workaround and you’ve found Dataview useful! dv.func.link() is also a good alternative here.