Closed KITMohi closed 2 weeks ago
Hello, thanks for the report :) Could you tell us what the actual anchor is when you serve your docs? VSCode probably doesn't slugify the same way as Python-Markdown does.
Yep, here's the anchor I get when serving my docs with a Conclusion & Future Work
heading: #conclusion-future-work
. In short, the anchors generated by VSCode do not match the ones generated by MkDocs. So the anchor validation warning is right. I'd recommend always checking the anchors by serving your docs and looking at them in a browser. I'll close this but feel free to comment further!
Hi and thank you for the great project!
I've noticed an unexpected behavior with the new anchor validation features where headers contain special characters, specifically "&".
Here is a reproducible sample with 1.6.0
mkdocs.yml
:docs/index.md
And here's the error I get:
It's worth noting that it's a TOC generated by VSCode.