marcusolsson/obsidian-projects

Support to YAML objects

Opened this issue · 2 comments

hyungtaecf commented

What would you like to be added?

Support to target nested fields.

cartParams:
  - title: Leg type 
    options:
      - Round
      - Square

Allowing properties like cartParams.title to show in the result.

Why is this needed?

This enhancement would enable users to organize their frontmatter in a more structured manner, especially in cases where a vault serves multiple purposes and involves a significant amount of frontmatter. Utilizing object-like structures for properties, such as the example provided, offers a cleaner approach to managing data, prevents cluttering of property lists, and facilitates the separation of different types of notes that share the same property name. Additionally, this enhancement aligns well with plugins like Dataview, allowing for more versatile and powerful usage scenarios.

Acylation commented

Yes the structured object is a common case. However, regarding this is not yet supported by Obsidian Properties, I would wait for an upstream solution, or at least put this aside for a certain term. See https://forum.obsidian.md/t/properties-support-multi-level-yaml-nested-attributes/63826

bean5 commented

@hyungtaecf I agree with @Acylation that waiting for upstream support would make this easier. Right now Obsidian itself stores the metadata of properties (type) separately from values AND I haven't seen needed fields work in Obsidian. In fact it breaks.

If this project was to adopt support for nested fields it would have to use a work around such as markdown comments. In the end, the data would be inaccessible by Obsidian itself as a property.

I suggest opening a request with Obsidian team. See https://help.obsidian.md/Help+and+support