Text field (or a single item in a list field) only allows either text or a single link.
Links should be interpreted like they are in the note’s body.
Make a list property and put parts of the text and links in items of it, but that’s unfriendly to manipulating properties programmatically and it’s unwieldy.
This should also apply to markdown links if they are (hopefully) implemented.
THis seems to be an interesting idea. I think it would be useful in some cases for video making for example.
This seems to be covering the same topic as Cannot Include Text and Link in the same Text Property Value.
Feature requested:
For a text type of property, allow to interpret the value as a single line of markdown.
Allow describing something with a sentence as a property. Here are a few
For the UI of Obsidian to recognize the line of text value of any property to be a markdown.
Ignoring the markdown, just treat them as plaintext
Hi there,
yes, that would be a great feature!!!
@WhiteNoise: you closed the feature request https://forum.obsidian.md/t/cannot-include-text-and-link-in-the-same-text-property-value/65958/7 and linked it to the feature request of this thread and marked it as “solution”… => does that mean, that this feature request will be implemented in future releases?
Thanks in advance,
Silias
I, too, would like to know. This is a feature the absence of which hinders the usefulness of properties unnecessarily, IMHO.
I closed that thread and pointed to this one because it’s a duplicate.
I understand. I was just adding my voice to the idea under discussion, not trying to criticize a valid moderating decision. Thank you for your work as a moderator.
This would be nice. It’s unintuitive that text outside links breaks them, and this lessens the versatility of Properties.
I would like to express my support for this request: it is one of the two great lacks I feel in Obsidian!
hi @WhiteNoise
right now that Bases is out. this feature is more useful and important.
Allowing string and backlink in text property so when in Bases you can view and click easily.
One workaround for this I have found decent is to create a text property (in my case “changelog”) and link to a block in the note’s body. This way you can write as you would normally in any note while still being able to query it via Properties from Bases Views.
I want to add some formatting to specific columns in a base table.
Maybe treat all text as Markdown by default. Or add a function that specifically renders markdown in a string. I don’t have a preference here.
There are also other things that can be achieved with this:
I used this extensively with inline dataview properties and associated queries. This is a must-have IMO. Currently very frustrated as have been effortfully converting to yaml properties as required by Bases, and now encountering this gap.
I don’t have an opinion on the request, just posting this relevant bit from the docs:
- Markdown in properties: This is an intentional limitation as properties are meant for small, atomic bits of information that are both human and machine readable. (https://help.obsidian.md/properties#Not+supported)
(But the request hasn’t been closed, so presumably you can still hope.)
