optionally persist implicit targets in objects.inv

[mikemckiernan]

Describe the feature you'd like to request

Any appetite to persist the implicit targets in the objects.inv file?

It's clearly some overlap with autosectionlabel. The key difference is that the intersphinx references in other projects would more closely resemble the local project references.

I haven't looked too closely at what it would take, but I'd be willing to if the thought has any traction.

Describe the solution you'd like

By enabling some myst_-prefixed option, the objects.inv file includes the implicit link targets according to the myst_heading_anchors value.

A link target within the project, such as [](somefile.md#general-options) would more closely resemble an intersphinx reference like {external+other-proj:ref} general-options. (Cowardly skipping the fight to render nested backticks.)

Describe alternatives you've considered

I suppose an alternative is to update autosectionlabel to use the slugging function from this package.

[mikemckiernan]

I spent some time today getting autosectionlabel to support a slugging function, a ripoff of myst_heading_slug_func. After having done it (with tests!), I'm fairly sure that'd be a misstep.

As-is, autosectionlabel supports syntax like :ref:A Plain Heading. Enhancing that extension to add a "index:a-plain-heading" link target to objects.inv (just because it's used in concert with this extension) would be wrong.

I'm back to my original thinking--it'd be nice if generate_heading_target (or some better approach) were enhanced to support persisting those targets.