TypeScript errors are multiline but do not surface in the editor or problems view

[bpasero]

I am starting to selfhost on running the gulp tsb task in the workbench. Since errors are multi line, I am missing important information I had before:

Neither are the multi line errors showing up in the hover in the editor nor are they showing up in the problems view.

Marking as important because this makes my selfhost unusable with this setup.

[sandy081]

@bpasero so the markers are not having the complete information?

[bpasero]

@sandy081 the output was showing multi line error and the marker was showing single line in hover and problems view. Not sure if this is a UI problem or marker problem.

[bpasero]

I pushed a change to use the markers only for closed documents (d9491c0). I will report back if this improves my experience.

[sandy081]

@bpasero What is the impact after your change?

[bpasero]

Sorry, not using this anymore from within Code. Got so used to my terminal outside :-/

[dbaeumer]

Actually addressing this might cause some work inside multi line problem matchers. Multi line matchers are made for a use case like

Errors in file A.ts
1,1: An error on line one
2,1: An error on line two

I will keep this as a feature request but I think we would benefit more from a project wide TS builder than addressing this use case in the problem matcher.

[ncannasse]

That seems like a important fix indeed. Actually our Haxe compiler integration is having issues with long error messages being cut, and there is not much that can be done on our side, see vshaxe/vshaxe#137

[alexr00]

Would be solved by #59337. Otherwise, out of scope.

[vscodebot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!