Results 216 comments of Moritz Jung

A text view field will already display a list property separated by `, `. ```md --- foo: [1, 2, "bar"] --- `VIEW[{foo}][text]` ``` Will display as `1, 2, bar`.

As stated here https://github.com/mProjectsCode/obsidian-meta-bind-plugin/issues/459#issuecomment-2474934806, I am leaning towards an argument that displays the first alias when available. `option(value, name, description)` seems interesting, though I am unsure if this is needed...

i haven't tested this, as I am on vacation, but if this only happens in some special excalidraw thing, then most likely excalidraw is at fault

I don't think this is a very valuable addition as (like you said yourself) it is already possible via CSS snippets. I will probably not work on this in the...

with the addition of inline CSS styles in `1.2.5-canary.20241127T230712` this FR seems somewhat fullfilled.

What do you mean by "not work"? Could you be a bit more specific? `null` works as intended ![image](https://github.com/user-attachments/assets/201b37de-8d89-428b-b3eb-0b1b892a4776)![image](https://github.com/user-attachments/assets/99b6fafd-cadd-4396-b92d-3233bf80d9d2)

I can't reproduce this. Maybe it got fixed somehow.

I don't think this would be a good addition to the plugin. First and foremost, it adds special cases to an already relatively complicated system, making it even harder to...

There is no API for properties yet. I will only consider FRs that rely on an API for properties, when said API is available in Obsidian.

This would fall under #317