Oh hey, quick note, I figured out how to accomplish what I wanted using the Dataview plugin, accomplishing my original goal. I still think supporting this is important, but my main use case has been resolved.
1 Like
The feature request is tagged as “valuable”, so maybe there is hope, even if there wasn’t any update for a year.
At the same time, it may not be YAML compliant which may explain their reluctance to implement this (even if some status or update concerning this FR would be nice to have).
To solve this, we could have an option to turn on or off aliases in the YAML, for those who really want aliases in their YAML, either in external (URL) or internal (wiki) links. So by toggling the option ON, we would finally have the nice formatting, and by toggling it OFF we could export to other markdown software if ever needed.
There are so many notes that require URL or Wiki links with aliases (because URL or Wiki link is either too long or require a more explicit name depending on the context where the metadata is) as metadata, that Properties feel kind of crippled without supporting this.
3 Likes
We wrote a post today to address the lack of response/why this is not considered question:
+1, thank you!
2 Likes
+1. Was surprised to found out I can’t put tidy markdown links in frontmatter, and must make do with plain URLs 
This is especially surprising because wikilinks, on the other hand, are supported in properties.
2 Likes
Added this feature in Plugin: Frontmatter Markdown Links - Adds support for markdown links in frontmatter
6 Likes
+1 k thx bye
Many thanks, that was desesperately needed ! I’ll finally be able to use Properties !
I just wanted to make my voice heard as well.
I rely heavily on links in the note properties and I would really appreciate if I could make them easier to read and distinguish. Some http urls get really long and difficult to understand like this one https://satechi.net/products/stand-hub-for-mac-mini-studio-with-nvme-ssd-enclosure/Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0VmFyaWFudC80MDc0ODI3MTYzMjQ3Mg== and some are simply difficult to understand because they don’t convey any context within them, like this one: https://www.imdb.com/title/tt6348138/.
Markdown links are already a great solution to this problem and I hope they will work in the properties in the future.
1 Like
+1 it just makes sense that properties should function the same as an external link in a regular note
3 Likes
+1!
Let me introduce some use cases here.
In addition to the official web clipper(which creates one note per website, one by one), there is many browser addons that can copies multiple tab titles and URL at once in markdown link into clipboard. If external markdown link is rendered on property, it will be very handy and quick way to add reference websites in note.
mnaoumov’s plugin is very useful also.
1 Like
Will be implemented in v1.11. No ETAs.
2 Likes
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.