Make compiler errors a little easier to read

[norpan]

I had a hard time reading the errors from Elm 0.19, because it uses color to signal the relevant information. However, it seems we can't have color in the vscode.Diagnostic, so I propose we put '#' around all parts of compiler errors that are decorated.

[norpan]

#number# here is the type that is wrong

[7sharp9]

Tooltips can have a colour and markdown, are the errors rendered entirely differently here?

…

On Mon, 27 Aug 2018 at 19:34, norpan ***@***.***> wrote: [image: hashes] <https://user-images.githubusercontent.com/1681354/44678369-81f4e180-aa38-11e8-856b-562cb0a60b4a.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#251 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAj7yju3cL351N9e3SrmxLw2J5JT1Qgrks5uVDuZgaJpZM4WORCC> .

[norpan]

Unfortunately yes, it seems that compiler errors can't be styled. Other hover popups can be styled.

[7sharp9]

@hakonrossebo What do you think?

[hakonrossebo]

I would say we could do this now, and it's easy to fix later if we find another solution.

[Krzysztof-Cieslak]

Thanks a lot!

[norpan]

A feature request with vscode to allow styling diagnostics is here: microsoft/vscode#54272

[razzeee]

The thing i don't like about this is that some messages use the '^' sign to mark an error. But this now gets moved 1 character to the right which might be wrong or confusing