Waylan Limberg

> I don't know any other thread that talks about this `f"{part}"` usage. @oprypin, for context, this is all about Python-Markdown using mkdocstrings for its API documentation. The `{part}

@pauloxnet thank you for listing some specific things that you would like to see supported/included in our documentation. I will note that I am very particular about some things and...

In my initial commit, I deleted a couple public functions which are no longer needed. I probably should have left them in and marked them as deprecated instead. Do we...

I finished updating the tests and documentation. I think this is ready to go.

@oprypin @pawamoy I wanted to check with you before I did a release of this. As this is a change in behavior that affects your projects (in that a bug...

Well, there definitely is interaction with mkdocstrings. According to my own testing, the [show_symbol_type_toc](https://mkdocstrings.github.io/python/usage/configuration/headings/#show_symbol_type_toc) feature breaks with this change. Presumably, mkdocstings will need to retrieve the value from `token['data-toc-label']` rather...

The primary concern for MkDocs is that the page title should not ever contain any markup (to avoid markup in `` etc). As the page title comes from `token['name']`, then...

Two other factors come into play, 1. For a theme to access `token['data-toc-label']`, then MkDocs needs to pass that on. I don't think it does (needs confirmation). 2. In mkdocs/mkdocs#3578,...

Prior to this present change, the assumption was that both `name` and `data-toc-label` never contained markup. It was a weird anomaly that this ever worked for you. Therefore, with this...

I'm sorry but I'm a little confused. Do you mean that the vim window needs refreshed? I suppose we could add a call to `:redraw` at the end if the...