Skip to content

Commit 6c2d3de

Browse files
committed
Fix some links in eep74
1 parent fc7995b commit 6c2d3de

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

eeps/eep-0074.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Rationale
4141

4242
The concept of an "Error Index" for a programming language is not a
4343
novel idea. Error catalogues already exist, for example, in the
44-
[Rust][] and [Haskell][] Communities.
44+
[Rust] and [Haskell] Communities.
4545

4646
Producing meaningful error messages can sometimes be challenging for
4747
developer tools such as compilers and type checkers due to various
@@ -85,15 +85,15 @@ additional, information about the error that would not be practical to
8585
present directly to the user. Here is an example of what the entry
8686
could look like for the above code:
8787

88-
![Erlang Error Index Sample Entry][]
88+
![Erlang Error Index Sample Entry]
8989

9090
Unique diagnostic codes also have the advantage to be better searchable in
9191
forums and chats, where the exact message could vary, but the diagnostic code
9292
would be the same.
9393

9494
Finally, diagnostic codes can be used by IDEs (e.g. via language servers)
95-
to match on diagnostic codes and provide contextual help. Both the [ErlangLS][]
96-
and the [ELP][] language server already use "unofficial" error codes.
95+
to match on diagnostic codes and provide contextual help. Both the [ErlangLS]
96+
and the [ELP] language server already use "unofficial" error codes.
9797

9898
Implementation
9999
==============
@@ -362,7 +362,7 @@ diagnostics should produce diagnostics (errors and warnings) in a
362362
standardized parsable format. This should be done
363363
by specifying an extra option (for example `--error-format json`).
364364

365-
A possible JSON format, heavily inspired by the [LSP protocol][], is:
365+
A possible JSON format, heavily inspired by the [LSP protocol], is:
366366

367367
```yaml
368368
{
@@ -388,7 +388,7 @@ A possible JSON format, heavily inspired by the [LSP protocol][], is:
388388
Where:
389389

390390
* **uri**: The path of the file the diagnostic refers to, expressed using the
391-
[RFC 3986][] format
391+
[RFC 3986] format
392392
* **range**: The range at which the message applies, zero-based. The range
393393
should be as strict as possible. For example, if warning
394394
the user that a record is unused, the range of the diagnostic should
@@ -497,7 +497,7 @@ license, whichever is more permissive.
497497
[Erlang Error Index Sample Entry]: eep-0074-1.png
498498
"Erlang Error Index Sample Entry"
499499

500-
[Erlang LS]: https://github.com/erlang-ls/erlang_ls/blob/a4a12001e36b26343d1e9d57a0de0526d90480f2/apps/els_lsp/src/els_compiler_diagnostics.erl#L237
500+
[ErlangLS]: https://github.com/erlang-ls/erlang_ls/blob/a4a12001e36b26343d1e9d57a0de0526d90480f2/apps/els_lsp/src/els_compiler_diagnostics.erl#L237
501501
"Erlang LS using error codes"
502502

503503
[ELP]: https://github.com/WhatsApp/erlang-language-platform/blob/99a426772be274f3739116736bb22d4c98c123c4/erlang_service/src/erlang_service.erl#L608

0 commit comments

Comments
 (0)