Properties: Alias key gets changed to "aliases"

I think you need to go inside the properties.
But I wonder what Linter or plugins that update date modified would do to change it. Probably you need to go inside to have the YAML be rewritten.

1 Like

My head → :melting_face: and :exploding_head:


My head when trying to figure out where other people’s GIFs start and end: :melting_face: and :exploding_head:.

*Then Gino finds pause button and plays with it and not watch USA get beaten by Germany.*

1 Like

In the hope that this is a little clearer:


Ahm. Germany won.

1 Like

Obsidian is displaying the non-deprecated versions of deprecated property names (that it still recognizes for backward compatibility).

I would expect it to rewrite them if you use the properties UI to change the note’s properties and to not rewrite them if you edit outside the UI.


Just the file being worked on. The properties UI shows you the properties of the current file, you change them, and it saves those changes to the current file in the standard format that it uses (which may change the existing format if the existing format was written by hand).

1 Like

I thought the idea was for Obsidian to sanitize the entire vault, so I assumed that all files would be checked and rewritten (if necessary). A mix (if that is what is happening) of sanitized and not-sanitized seems a little odd … in my tiny mind.

I’m wondering if there’s some kind of OR solution to my alias v aliases problem…

currently one of my table columns is list(org, alias, note) - which works on files that haven’t had that property changed to “aliases”. I’ve tried a couple “OR” permutations thus far, but neither have worked:

  • list(org, alias OR aliases, note)
  • list(org, (alias OR aliases), note)

Anyone know whether I’m barking up the wrong tree entirely?
Would love to not go through & find/replace thousands of files, but could embark on that if necessary.

Please start a new thread for that question. Thanks!

1 Like

A goal of the new setup is to prevent users from writing bad YAML, but the reformatting of existing YAML is largely a side effect. YAML is horribly complicated and has numerous ways to write any given thing; Obsidian doesn’t preserve the exact formatting when it writes back to your file. From API: processFrontMatter removes string quotes, comments, types, formatting - #6 by Licat which I linked earlier:

The decision we made is for plugins to be able to interact with frontmatter easily. We do this by converting YAML into a JS object, which means it lose all of its YAML specific formatting and comments. This makes it easy for plugin developers to read and modify properties of a note, without requiring them to interact with an excessively complex YAML syntax tree, which would require them to understand how YAML is parsed internally.

Thanks for the reply and additional advice.

I have decided to move my notes to a different app.

As you are a moderator, can I ask you to close (delete, lock, anonymize, or whatever is possible) my forum account so that my personal data is removed / locked against future use?

Thanks in advance.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.