[Maybe FR] Is there a way to insert before a heading?

[Moyf]

Question

Currently, is there anyway to insert content Before a sub-heading?

For instance, consider this example from the API Doc:

# Heading 1

This is the content for heading one

Also references some [[#^484ef2]]

🎯 <!-- I want to put content here. -->
## Subheading 1:1
Content for Subheading 1:1

### Subsubheading 1:1:1

I tried:

• append to Heading 1:
  • The content will be placed on the end of the whole heading, after all the sub-headings.
• prepend to Heading 1::Subheading 1:1:
  • The content will be placed on the line under the sub-heading.

Could you please teach me how to put the content before the line of a sub-heading?

Or, if not, could you consider adding an option to append (ignore sub-headings) ?

---

Context

I'm using the following structure to record my time in my Daily Note:

# 2025-04-11

## Timestamp
- 12:00 some things
- 13:35 some other things

### Time analysis
```dataviewjs
// Code to analyze the time expenditure.
```

I would like to use REST API to insert new timestamp records into the list under ## Timestamp (before ### Time analysis), but I haven't figured out how to do it.

[coddingtonbear]

I remember you! You requested this kind of feature a while back. Unfortunately, that particular use case hasn't came up from other folks, and I don't have a personal use for such a type of patching; so I won't be able to commit the time figuring out how to approach such a thing.

If you were personally interested in figuring out how to implement such a thing and take your concept from an idea all the way through to a coded pull request, there are a few things you'll want to keep in mind:

1. Patch instructions handled by this library are actually handled by https://github.com/coddingtonbear/markdown-patch; so your work would begin there.
2. In markdown-patch, your document is organized into a set of "targets", and those targets are meant to correspond with semantic chunks of your document (i.e. headings, marked blocks, frontmatter fields).
3. It isn't clear to me right now how you might approach your particular case in that kind of model given that semantically the subheadings are part of the semantic chunk of their parent heading, but I'm open to hearing ideas.

I wish I could help out more than this, but time is precious! I recommend starting a discussion on the markdown-patch discussion board before you get started on anything around this just to make sure we're on the same page about the approach you end up taking before you make a big time investment yourself.

Cheers!

[Moyf]

Hahaha, this is simply unbelievable, your memory is really good!
In fact, when I initiated the Issue, I specifically serached for msyself in both the Issue and Discuss sections using the Author: @me filter (becuase I also had the impression that I had provided feedback before) - But I couldn't, Iso I thought it might be a false memory.
But I never expected it to be in the comment section! You really got me there 😂

Thank you for your patient guidance and instruction!
I'm trying to convice myslef to modify the structure - extracting the sub-heading to avoid similar needs.
As you said - time is precious!
Rather than diving into unknown areas for development, it might be easier to let go of some past structural obessessions 😖

---

Speaking of which, I also wanted to share another observation:
During my recent attempts to use REST API, I noticed that Obsidian's note updates are delayed.
When I send a request via HTTP and receive a 200 status code, I can see from the Github client that the file has actually been modified, but the note in Obsidian remains in the state before the change.
I'm not sure if anyone else has reported this phenomenon - or if it's just happening to me?

(And sometimes, even after receving a 200 status code, the change aren't actually added into file successfully. This happens occasionally, and I haven't been able to identify a pattern yet...)

---

Anyway, thank you again for developing such an useful plugin! 🫡