Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using explicit language identifiers in generated markdown code-fences #694

Closed
the-mikedavis opened this issue May 20, 2022 · 0 comments
Closed

Comments

@the-mikedavis
Copy link

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

```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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant