Perhaps you have heard of “templates.”
In the past, it could parse correctly.
In fact, there’s not so much “unfortunate” here. All of this is not a reason to change user data; there’s no need for someone to tell us how to take notes, what format to follow, and enforce conversions. I’m not sure if this aligns with “for you.”
I’m not a technical person, but since my YAML can be recognized and forcibly converted, could an API be provided to plugin developers instead of using them as a scapegoat to shift the conflict?
In previous versions, my aliases and tags could be correctly parsed, so I don’t think there’s a need for it to be forcibly formatted. Could an option be provided to completely disable Properties? It greatly affects my batch processing. I don’t want my data to be silently changed every time I insert a template or perform any operation, and if there’s YAML in my template, it can’t even be fully inserted.
Alternatively, could you consider my following suggestion: YAML is left to Obsidian, but please optimize “Inline Fields” so that aliases and tags within it can be parsed.