Do errors need to be in Errors Window?

[harsimranb]

It would be great to have Errors in the Errors window, but I'm not sure if that's the desired functionality. HTML, ASPX, XML errors don't show in the errors window. Infact, only C# errors after failed build show in the errors window.

[mhutch]

There are three "classes" of errors/warnings in MD. I'd recommend sticking to these error classes so that the UX is consistent.

1. Compile time errors/warnings, emitted by build tools when compiling the projects. These errors cause the build to fail. They are shown in the error pad, and in the source editor as "error bubbles", which are very intrusive.
2. Parser errors. Errors emitted by any text editor parser are automatically show an "red squiggle" underlines in the source editor and in the vertical scrollbar.
3. Code issues from the source analysis system. These can use a whole range of markers, they can grey out the text (e.g. unreachable code), mark text red (e.g. unresolved members), use blue underlines (suggested improvements), etc. These markers are also shown in the vertical scrollbar. Uses can use the "code issues" pad to scan all files in their project for code issues.

So right now you just have parser errors for JS, but in the future it may make sense to add source analysis issues.