[Question/Feature request] Show the list of errors using visual studio code editor

[bastienJS]

I can`t find a way to show the list of typescript build errors in an error list, like it works in visual studio 2015.

My motivation is that I do not want to click in each file to see the build/intellisense errors...

I would like to have a list of those errors in an integration window.

[Tyriar]

ctrl+shift+m is the shortcut for showing errors and warnings in all files. You can also click the icons with the numbers at the bottom of the screen

[bastienJS]

@Tyriar Is there any chance of making the error "dialog" pin-able to the bottom/top? Maybe its already in the 1.2.0 release? I do not want to jump from one error file press "control/shift+m" and do this in page having a build error.

I am just doing a migration of Angular beta2 to rc1 with many errors, a pinned window with all errors would allow a much better workflow :-)

[Tyriar]

@bastienJS I don't think it's possible right now, you can file an issue specifically for that "Show errors/warnings in 'pinnable' panel" (or something) and it will get routed to the right person 😃

[bastienJS]

@Tyriar Hey hey quick answer ;-) Ok I will do that, thanks!

[Tyriar]

@bastienJS I'm most awake around this time 😉

[bastienJS]

@Tyriar Man I can`t wait for the 1.2.0 release with the integrated CMD :-)

=> #7074

[Tyriar]

@bastienJS you can try it out now on the Insiders build, pretty eager for feedback to come in! http://code.visualstudio.com/insiders

[bastienJS]

@Tyriar Just installed it. So I get the latest visual code artifact from each day? Thats cool man. So I can give quick feedback if I see change in the behavior good/ bad ;-)

[Tyriar]

@bastienJS I think the daily change is going live next week with the stable build

[bastienJS]

@Tyriar I already experienced the not available scrollbar due to term.js, I am surprised that this is a javascript implementation, never thought of that. Is there a special reason for it? Just curious...

[Tyriar]

@bastienJS the root cause of that is because only the current viewport is represented in the DOM, it's probably the right way to go to save creating so many elements but a scroll bar would definitely be handy.

[bastienJS]

@Tyriar handy? hehe that was said mildly ;-) Without scrollbar, but more than ONE build error, its not usable at least in that context. Just think the integrated terminal has a height of appr. 100px. When I run "ng build" with more than an error I can see only the last error, the rest is cut.

[Tyriar]

@bastienJS it's still possible to scroll though with the mouse wheel and ctrl+shift+arrow or ctrl+alt+page up/down (on Linux/bash anyway). If you weren't aware of this I'd be interested in the platform you're on and which shell you're using.

[timhyson]

Hi @Tyriar, is there an equivalent to this for zsh?

[Tyriar]

@timhyson page up/down should work, I opened xtermjs/xterm.js#181 to look into why the arrows don't.

[timhyson]

Ah ok, cool - I'm on a macbook pro, so fn + shift + ↑/↓ gets me there... Many thanks.

[kevinjreece]

@waderyan: Hey Wade. I see how to show errors and warnings for files that are currently open (ctrl+shift+m). But is there a way to show errors and warnings for all files, even closed ones? I just made a change that I'm sure broke lots of other files. I'm just not sure which ones. It would be nice to have a list of all errors to help me fix the errors I caused.

[echo-sean]

@kevinjreece I have done the same thing and had to look at the terminal to find the errors. I think it would be useful to show something (a red circle?) next to each icon in the file explorer to indicate an error. I wonder if this is something the icon theme extensions would need to support though?

[guillaume86]

I'm also highly interested in project wide typescript error checking.
Should I open a new issue dedicated to this? (is it the right place?)

[waderyan]

@kevinjreece not today as far as I know but this is a good feature request. Can you open a new issue? Definitely something I would like to see as well.

[kevinjreece]

@echo-sean: Showing a red icon next to the file in the file explorer would be useful for small projects. But in my current project, we have hundreds of files nested many layers deep in multiple sub-directories. So red icons wouldn't fully solve the problem for me. What I need is a list of the errors by file so that I can see them in one place and quickly click through them, just like the "Problems" section they currently have

[kevinjreece]

I just created an issue to formalize this discussion: #13953

[echo-sean]

@kevinjreece Sorry, I wasn't very clear. I meant as an addition to the problems section of course.

[jiayihu]

Is there any setting to automatically open the warnings/errors on save if there are any of them?