Skip to content

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

Description

@the-mikedavis

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions