Margret Riegert

I don't think this is possible to fix without tree-sitter or an LSP, due to the complexity of Heredocs.

Potentially useful: - https://github.com/elixir-lsp/vscode-elixir-ls/issues/46 - https://github.com/microsoft/vscode/issues/48332 - https://github.com/microsoft/vscode/issues/176694

https://github.com/microsoft/vscode/issues/583

This should work with v0.9.0-alpha.1, though it's reliant on the `crystal tool implementations` CLI tool. This can be unreliable when working on a libraries internals and I'm not sure why...

This fix has been published for some time.

Let me know if this still occurs on v0.9.0

The underlying crystal tools don't support using wildcards for the main file, so there's nothing to do here. As well, the extension is moving away from using a configuration to...

I have this working on [this branch](https://github.com/nobodywasishere/vscode-crystal-lang/tree/markdown_code_block): 

It looks like there's a Markd option that could fix this if enabled: https://github.com/crystal-lang/crystal/blob/d0ad0275eb9db4f9a40dffc8d9825eac46eeb36b/src/compiler/crystal/tools/doc/generator.cr#L323C35-L323C35 https://github.com/crystal-lang/crystal/blob/d0ad0275eb9db4f9a40dffc8d9825eac46eeb36b/lib/markd/src/markd/options.cr#L51C15-L51C15 I'll have to test and see what this outputs though to see if it's safe...

After discussions on the discord server, I think the best option is as follows: - Escape all html in doc comments (safe by default). This prevents accidental html tags from...