Output to YAML frontmatter

[Taitava]

Obsidian 1.1.0 has a new metadata API that looks like an easy way to modify YAML frontmatter sections of e.g. the current file.

Imagine the following YAML section:

---
tags:
  - aTagThatWillDisappear
deletableValue: "Goodbye!"
myValue: "This text will stay."
---

I'd like to create a new output channel that would interpret the output content, letting it to perform different kinds of actions on the YAML frontmatter:

• Set YAML value, e.g. tags: [tag1, tag2]
• Delete YAML value, e.g. -deletableValue
• Delete all YAML values *overwrite* (only applicable if defined as the first line of output). Meaningful if the aim is to write a new YAML section from a scratch.
• Add to YAML value, e.g. tags+: newTag creates a new list item, or if it's a single value instead of a list myValue+: " Added text."
• Anything else?

These actions would turn the above shown YAML example to:
(*overwrite* is not taken into account.)

---
tags:
  - tag1
  - tag2
  - newTag
myValue: "This text will stay. Added text."
---

The syntax is just a quick draft idea, I haven't made any decisions on it yet.

Multifile editing

Maybe also make it possible to alter multiple files' YAML sections? Syntax example:

File path here, or @ if it's the currently focused file.
Another file path here. (In case same alterations are wanted to be done on multiple files).
---
tags: [tag1, tag2]
-deletableValue
---
Third file path here.
---
tags+: aTagThatWillBeAddedToTheThirdFile
---

[BeCracked]

I am running into this now. I use this to set a tracking value in my daily notes, so I need to do it quite regularly. But doing it with caret position doesn't work when not in source mode, and using clipboard seems like a crutch.

Rudimentarily, it could be implemented similarly to #382 with a JSON object simply mapping the values. Not sure how to best implement the other features you mentioned here, like delete.

[BeCracked]

Another idea that just popped into my head is to have a link to a command (like I have seen here before) and have it replace itself. Just a thought :D

[Taitava]

Hi and thank you for your message! 😎

Yes, JSON makes sense here, too. I still need to figure out the syntax (even though if not implementing all features in the first version), so this is not going to happen any time soon. 🙂

Todo for me:

• Rewrite my first post's syntax examples to use JSON.

Another idea that just popped into my head is to have a link to a command (like I have seen here before) and have it replace itself. Just a thought :D

Oh, true, that could be possible! 😄