I expect nothing to happen except for the template text to be added.
Actual result
The array in the YAML is converted into a list.
Environment
SYSTEM INFO:
Obsidian version: v1.4.5
Installer version: v1.3.5
Operating system: Darwin Kernel Version 22.6.0
Login status: not logged in
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: on
It depends on how you look at this issue. Both of those are semantically equivalent. The former is flow notation of YAML using JSON, the latter is âpureâ YAML.
I understand that both formats are valid, but please do not alter my data. I have already disabled the Properties view, but my data is still being modified, which disrupts my previous script, and it will be difficult for me to make bulk changes using VSCode + regex.
I donât think these two FRs are discussing the same thing. I just hope Obsidian can recognize aliases and tags in âInline Fieldsâ and wonât change their format arbitrarily. aliases and tags are the keys most likely to have multiple values added, and they will interact extensively with Obsidian.
@Nico I can see your frustration but the app is still âfor you, foreverâ. You can simply roll back to an earlier version of the app and continue to use that one.
Another option, and the one I am going through, is to make changes to my files - slowly as I come to them - and move forward with the app as it grows and evolves.
Actually, this has set a bad precedent - give them an inch, and theyâll take a mile.
I know speaking up here wonât really make a difference, but scribbling something down is still better than playing the ostrich.
While âPropertiesâ may appear unattractive and intrusive to me personally, it is a necessary step for commercial viability and to better cater to habitual Notion users. As for the niche group that prefers batch processing, well, who cares? After all, who can resist the allure of large clients?
Alright, maybe I didnât explain it clearly, but the main issue here is that my content is silently altered without any warning. It could happen when I insert templates, merge files, or even in the future when I paste text.
Now, even when I insert a template with YAML into a blank document, my YAML often gets changed.
This leaves me with a profound sense of frustration. I mean, I might be able to deal with it, but why should I have to go through this extra work? I just donât quite get it.
Itâs also worth considering whether Obsidian is now the right solution, considering your specific need.
Have you ever looked at VSCode plus the various live markdown and Foam-like plugins? You can create a very similar all-open-source experience. I had a look at it a month or two ago and it was very decent.
I indeed donât know how to use a YAML parser. Typically, I rely on VSCode and regex to make document modifications. Occasionally, I use Python to batch-create documents and initialize or split books. After all, I have tens of thousands of documents, and I canât guarantee that my code is error-free. Using VSCode with a .gitignore setup gives me more confidence in my work.
If I wasnât clear in the previous post, I meant that you could replace Obsidian entirely with VSCode and some plugins which provide very similar functionality.
Just an option to consider if the frontmatter changing is untenable.
Do you think Iâm making this suggestion because itâs bad or too difficult to use? If thatâs the case, Iâd rather just move away from it and embrace other software, rather than spending my energy here.
If I offer a few suggestions to improve a dish that align more with my taste (FR) instead of demanding the chef to reveal their recipe (open-source), would the chef ask me to cook the dish myself and then judge my culinary skills?
