Prettier error display, like pretty-typescript-error extension

[WWology]

Is your feature request related to a problem? Please describe.
Error messages on complex types and functions can be messy and tricky to read and understand
For example

cannot use signup.GardenerCommandHandler (value of type func(b *"clockey/bot".Bot) handler.MessageCommandHandler) as handler.MessageCommandHandler value in argument to h.MessageCommand

Describe the solution you'd like
It'll be nice if we can have error display like in the popular vscode extension, Pretty Typescript Error
https://marketplace.visualstudio.com/items?itemName=yoavbls.pretty-ts-errors

So instead of the error above
We can instead display

cannot use

signup.GardenerCommandHandler

(value of type func(b *"clockey/bot".Bot) handler.MessageCommandHandler) as handler.MessageCommandHandler value in argument to h.MessageCommand

Something to this effect

[WWology]

A screenshot from the vscode extension that i talked about

[firelizzard18]

In what context are you seeing this error? Is it a diagnostic (squiggly red line) in the editor or something else? IIRC diagnostics are provided by the language server, gopls. Rich diagnostic messages would probably be most easily provided by gopls because (I think) it has access to the underlying error before it's stringified. But I'm not familiar with the details of the language server protocol and I don't know if it's possible for gopls to provide rich messages through the standard protocol, though I'd guess it is.

[WWology]

Hi,

The errors are coming from the squigly red line of the editor yes, Showing up in the problem tab of vscode, i'm assuming it's coming from the LSP when it detects compiler error.

I'm assuming gopls would be able to do some sort of check if it's running in an editor that's capable of ouputting rich diagnostic messages and then returning that, and returning the standard error message if it's not running in an editor capable of it?

[hyangah]

Upstream issue: microsoft/vscode#54272

The pretty ts error extension seems to implement a hover message provider that digests diagnostics messages and formats it. https://github.com/yoavbls/pretty-ts-errors/blob/main/src/extension.ts

Btw, if the error message came from the compiler, I don't know how perfectly gopls can reformat compiler's message.

[firelizzard18]

Btw, if the error message came from the compiler, I don't know how perfectly gopls can reformat compiler's message.

I just meant that it would be less difficult to implement with gopls vs with the extension since gopls will at least have some error type vs the extension just has raw text. But I agree, reformatting the compiler's message would be challenging if the errors aren't structured. IIRC they have some structure but not enough to make it easy.

[findleyr]

Yes, this feature is blocked on both (1) support for markdown diagnostics, and (2) more structured compiler errors
(though we could extract the error code and format a link, to start).