Pretty TypeScript errors

[zisra]

Check for existing issues

• Completed

Describe the feature

TypeScript errors should be formatted in a similar fashion as pretty-ts-errors.

If applicable, add mockups / screenshots to help present your vision of the feature

[d1y]

This plugin is a mandatory plugin for me in VScode. If Zed can incorporate it, that would be great, haha

[yoavbls]

Hi there, I'm the creator of pretty-ts-errors
I love Zed, and I would be happy to port it to Zed or collaborate on that.
I know that currently, extensions aren't supported, but I can export the plugin as a TypeScript LSP, and it'll automatically be supported.
The only thing that is missing from that is an option for advanced MD/MDX on hovers on Zed editor.

If someone on the Zed team thinks it's possible please reach me out 🙂

[coolemur]

Might be right place to note this: when error message is too long, it doesn't wrap, nor scrolls right, so it is impossible to see whole message or copy error message to clipboard.

Pretty error messages might solve this it one go.

And on top of that: there is no way to close these errors (?). Unless editor is reloaded (?) or other error is opened.

[nckre]

Enabling copy for TS errors would also be great. Currently only the code can be copied but not the error itself.

[ethndotsh]

Seems like extensions are a thing now - would love to see this!!

[yoavbls]

@ethndotsh As far as I know extensions could be just themes and LSPs for now, we'll need the ability to add/edit diagnostics like VSCode allows + custom render for them

[nezudevv]

This would be a fantastic addition. I am also having a hard time reading the returned errors. Maybe its just a side effect of me being used to the vs code plugin 😅

[nathansobo]

We should take a look at this. I agree that our TypeScript error rendering looks really rough relative to that plugin.

[vladshcherbin]

Surprised to see such unreadable error messages after using VSCode, the difference is night & day 😅

[ConradIrwin]

I'm working on redoing our inline diagnostics to use our markdown renderer, and hoping to get that merged early next week.

If someone wants to pair with me on building/porting the logic that takes the diagnostic from the language server and spitting out spiffy markdown, that would be fun. https://cal.com/conradirwin/pairing

[MichalBastrzyk]

Any updates on this 😅