Adam SP

Hello; I am also encountering this issue, where `[[toc]]` is replaced with ``; Windows 10 22H2, VSCode 1.77.2, MarkdownConverter 5.2.1. I have also found that the `markdownConverter.Parser.Toc.Indicator` setting doesn't seem...

Hi @manuth; Cheers for the response. I have uninstalled `Markdown Preview Mermaid Support`, and have also disabled the following other extensions: - `Instant Markdown` - `Markdown Checkboxes` - `Markdown Footnotes`...

Hi @manuth; It was the `Markdown Preview Github Styling` extension that was causing the issue for me; with it disabled, and all of the others enabled, TOC would generate correctly...

> Yes, that would help me a lot to keep track of it Thank you very much! Issue #218 has been created.

Hi @Turnerj, cheers for opening the conversation. I was actually thinking of giving that a go in my branch, and if it works without impacting the perf of the library,...

I've encountered circumstances where even attributes can change the compiler behaviour, and introduce a regression; not common, but I'm an overly defensive developer 😂 Happy to investigate the matter, and...

Thank you for the reply @KalleOlaviNiemitalo! Your insight is appreciated. We are using `"@context": "http://schema.org/"` for all typed nodes, but even with that the online [Validator](https://validator.schema.org/) identifies no error with...

I can confirm that the validator correctly identifies an error when fully qualifying the JSON key:  I can also confirm that the JSON-LD Playground: - drops the property entirely...

Talk about issue revival, but I have just hit this with basic auth to a WSDL service; any chance the maintainers are interested?

Hi @EWSoftware; Yes, I am very aware of the advanced capabilities of VSSpellChecker, as I have been using it for years now. I do have the built-in VS spell checker...