You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, markdown code-fences generated for documentation do not specify the language (example). I think this works fine in most editors since the editor will assume the code block's language is Elixir. Some editors don't have that behavior though and fallback to no highlighting. Other language servers I have used provide the language identifier explicitly: for example rust-analyzer and erlang_ls. It would be a very small change to use explicit
```elixir
```
blocks instead and I don't see any downsides.
What do you think? Would you accept a PR here and in elixir_sense that adds elixir to code-fences?
The text was updated successfully, but these errors were encountered:
Hello! 👋
Currently, markdown code-fences generated for documentation do not specify the language (example). I think this works fine in most editors since the editor will assume the code block's language is Elixir. Some editors don't have that behavior though and fallback to no highlighting. Other language servers I have used provide the language identifier explicitly: for example rust-analyzer and erlang_ls. It would be a very small change to use explicit
blocks instead and I don't see any downsides.
What do you think? Would you accept a PR here and in elixir_sense that adds
elixir
to code-fences?The text was updated successfully, but these errors were encountered: