Like the TypeScript extension, the Haxe extension injects its grammar into markdown code blocks, and then also injects the markdown grammar into its own doc comments. This allows syntax highlighting like this:
This screenshot is from VSCode 1.34 after which point something seems to have broken / changed. Starting with VSCode 1.35, the @param after the code block is no longer highlighted (even though there were no changes in any of the grammars involved):
Evidently, it doesn't consider the fenced markdown block closed:
Source for easy copy-paste:
class Main {
/**
```haxe
trace("Test");
```
@param foo bar
**/
static function main() {}
}
Like the TypeScript extension, the Haxe extension injects its grammar into markdown code blocks, and then also injects the markdown grammar into its own doc comments. This allows syntax highlighting like this:
This screenshot is from VSCode 1.34 after which point something seems to have broken / changed. Starting with VSCode 1.35, the
@paramafter the code block is no longer highlighted (even though there were no changes in any of the grammars involved):Evidently, it doesn't consider the fenced markdown block closed:
Source for easy copy-paste: