Thanks for the PR! I think this makes sense but can you also add some tests to make sure we are doing the correct thing and don't regress this in the future:

One thing actually: we need to support@example without fenced code blocks:https://jsdoc.app/tags-example.html

For those cases, the text should be treated as if it was a code block even though there is no explicit fenced code block

@mjbvz am I missing something obvious here? I tried to follow the instructions athttps://github.com/microsoft/vscode/blob/main/test/unit/README.md to run the tests (with--grep typescript.previewer since there are entirely too many). This command can't seem to find the tests.
Running withyarn run mocha --ui tdd --run ./extensions/typescript-language-features/src/test/unit/previewer.test.ts can't find the file (it replaces the ts extension with js). If I try to run the built file in a way that I'd expect to work,yarn test .\extensions\typescript-language-features\out\test\unit\previewer.test.js, it can't findvscode

You can run them through VS Code's debug view:

Thanks! No wonder I didn't see that... have never really heavily used the debugger for tests.

Test cases:

/** *@example * foo(); * *@example * Caption * ```ts * foo(); * ``` */functionfoo(){}

/** *@example <caption>Caption</caption> * bar(); * *@example <caption>Caption</caption> * ```ts * bar(); * ``` */functionbar(){}

Disabled tests were failing, unrelated to my changes.

Thanks! This change will in the next VS Code 1.62 insiders build