Why nested YAML aren't treated like YAML?

[rohanbatraio]

I was wondering to make a decent system for tracking everything. For that nested tags are the best options to clutter free my YAML. So i thought why not go with that, but dbfolder doesn't seem to work as beautifully as it works in tags form. What i was expecting is to enable me add nested tags in the same way as adding it in case of tags, so that the datasource would be different and UI remains the same. Here's what i mean

See the tags "as genre" here?

demo.mov

Same i was expecting with nested tags, how?
Here's how -> adding a nested tags query as a column would solve the problem and would be awesome to have. Would really stress on this feature being possible here.

[rohanbatraio]

Why would we consider this ?

Here's what my workflow implies :-

For ex. lets say , I am doing academics, health, meetings etc things in a day. Now all that belongs to a day, which is a date, so its general to have all that info reside in a daily note.

Now i would like to make 3 databases (dbfolder) , 1 for each. and add specific column in each of them. For elaboration :

Academics would have academics related yaml
Health would have its columns and so on.

But ultimately all of that would go into one single daily note, imagine having 100's of individual yaml entries just so that you can have all features of DBFOLDER and are forced not to use nested yaml.

So for a clean approach i would request the solution i shared in the beginning of this discussion.

[RafaelGB]

to finally understand it. The tags would admit nesting under the nomenclature you share

The requirement is that the column has as id tags. Another option is to use inline mode and add # at the beginning of the word

[rohanbatraio]

it is not designed for the way of including tags that you propose

So what are your thoughts on the way i propose it?

[RafaelGB]

the problem with including / in ids is that it doesn't follow yaml standards and can break them. The way it has been proposed in 2.7.2 is to create complex objects and make nesting more flexible

[rohanbatraio]

The way it has been proposed in 2.7.2 is to create complex objects and make nesting more flexible

Yes i am updated with #442

the problem with including / in ids is that it doesn't follow yaml standards and can break them.

Why not to follow YAML standards? Why not just go with ->

YAML :
- NESTED_YAML : KEY
- NESTED_YAML2 : KEY2

and we would parse it with

yaml:nested-yaml -> with double quotes if any programming syntax sanitation is required . instead of yaml.nested yaml.

[rohanbatraio]

or parsing could be done as described here ->
https://user-images.githubusercontent.com/113782197/196100578-fd92942e-84c2-49b7-a107-a88cbac086c8.png

[rohanbatraio]

Is there a specific reason you are using field.myNestedField ?

instead of field/myNestedField OR field:myNestedField

[RafaelGB]

YAML :
- NESTED_YAML : KEY
- NESTED_YAML2 : KEY2

this format is readable for yaml, but currently the plugin does not have any types for lists of objects, only lists (tags)

Making a list of objects is a new and quite complex interface. I can't think of an easy way to implement it.

[rohanbatraio]

2022-10-17.18-11-24.mp4

[rohanbatraio]

High possibility i did something wrong here!

[RafaelGB]

its not the way the nested yaml works.

You are reading the entire object selecting YAML and tags only accepts a list as an input

If you want to use a nested attribute as column, you have to rename the id first. In your example

object:
  nestedAttribute:
    - A
    - B
    - C

Then in your column config rename the id with object.nestedAttribute

[rohanbatraio]

Thanks for correcting me again @RafaelGB , I think i would stay away from nested YAML and skip it entirely for use of inline fields. Far better choice for me.

[RafaelGB]

happy to help! Its the first iteration of nested fields, will be improved with the time