What are the chances of enabling this Markdown extension (which is included in the standard library)?
The primary use case (for me at least) would be to add IDs to headings (and possibly other elements) when writing documentation, so as to be able to make my own links within a page (e.g. a custom Table of Contents, linking between pieces of documentation, etc.)
I know the unfortunately named HeaderId extension already does something to accomplish what I need, but it also means that any time a heading is changed (e.g. fixing a typo), all references to it must also be fixed, which can be cumbersome for anything but a small file.
I'm aware of the potential consequences of doing this, and possible clashes with your own element IDs, but the headings already do have auto-generated IDs, and I've just confirmed that, e.g. ## User dropdown trigger as a heading generates:
<h2 id="user-dropdown-trigger">User dropdown trigger</h2>
...which does clash with an ID already present in your own HTML.
So since it's already possible to have these kinds of conflicts, and you obviously rely on users not to break stuff intentionally, could you maybe enable the extension in question, giving users more freedom when writing Markdown?
Thanks in advance for taking the time to consider this.