The main issue was that inclusion of the @ symbols in plantuml code blocks made vscode.executeDocumentSymbolProvider return a strange/mistaken symbol with an unexpected kind: symbok.kind = SymbolKind.Object which messed up TOC generation.
Since Markdown headers are expected to only be strings, filter the symbols at their generation point and limiting them to strings seemed to be the simplest clean change. This is done in HeaderManager.ts in function getDocumentSymbols.
While testing the updated extension locally, I ran into packaging issues: vsce no longer allows svg images from https://vsmarketplacebadge.apphb.com. Updated online instructions ask to use https://vsmarketplacebadges.dev instead. Some additional misc changes were also made.
Update version to 3.0.13 via npm --no-git-tag-version version patch
Fix for Issue #60
The main issue was that inclusion of the
@symbols in plantuml code blocks madevscode.executeDocumentSymbolProviderreturn a strange/mistaken symbol with an unexpected kind:symbok.kind = SymbolKind.Objectwhich messed up TOC generation.Since Markdown headers are expected to only be strings, filter the symbols at their generation point and limiting them to strings seemed to be the simplest clean change. This is done in
HeaderManager.tsin functiongetDocumentSymbols.While testing the updated extension locally, I ran into packaging issues:
vsceno longer allows svg images from https://vsmarketplacebadge.apphb.com. Updated online instructions ask to use https://vsmarketplacebadges.dev instead. Some additional misc changes were also made.npm --no-git-tag-version version patchtests/code_block_test_plantuml.mdTesting