Properties: Support INTERNAL Markdown links

Feature requests
26

What if the property is just stored as a string? Wouldn’t that fix the compatibility issue? Isn’t that what Obsidian’s Properties feature is already doing?

Like this:

‘’’

  • parent:
    • child: “[[link]]”
    • child2: “another link”
      ‘’’

This way:

  1. It’s simpler for other apps to add compatibility
  2. It’s still valid yaml, and markdown
  3. It’s human readable.
1 Like
27

+1 This would be very useful especially in the case documents need to be converted in pandoc

3 Likes
29

I like to support this feature, I also proposed a more general feature request here:

https://forum.obsidian.md/t/text-type-property-to-support-single-line-markdown/72892

2 Likes
30

+1 for this, would love to have some human-readable lists of URLs as a property

3 Likes
32

I would like this feature as well. I have been looking for a solution for a while now before finding this thread.

33

+1 for this essential feature request. Any news please ?

Was finally going to convert to the new Properties today, only to discover neither external nor internal markdown links with aliases are supported. And yet, it’s so frequent to need a name/shortcut for a link (especially for url) as metadata in a note.

Will stick to the old and less UX friendly key:: for now.

34

I have split this FR in two parts for internal and external

5 Likes
35

+1 - Please add this!
It’s so badly needed,
and should hopefully be pretty easy to implement as it’s already working this way for wiki links.
Thanks :slightly_smiling_face:

36

Any news/ETA regarding this FR (and the same FR with external markdown links) ?

Thank you very much.