Better visual indicator that things are wrong

[PrzemyslawKlys]

Summary of the new feature

Right now when there is an error of sort VSCode the only visual indicator is the red file with a problem

Or none at all until you run it and it's too late.

Proposed technical implementation details (optional)

It would be great to show line where the first (I guess only 1st problem is visible, not all of them but if more then one, it would be great to see all) problem is more or less occurring. I sometimes see red file and then I search for a missing comma on 1000 line script. It's often easier to press F5, and see where it terminates.

[rkeithhill]

Have you checked out at the Problems view? Press ctrl+shift+m and it will show all detected problems in the script file, along with other files you have open. One thing the extension is not good about is removing entries from the Problems views after they have been fixed. Closing and re-opening the file will fix it but certainly is not ideal.

[PrzemyslawKlys]

I saw this problems tab but it's often hidden (as Terminal is my main one). Not sure if you can divide that screen into 3 separate screens.

Also notice that I sometimes (often) use the screen like that:

And notice how it only started to see problem after I added another function Test { } with an error. All errors above were ignored and not visible until I've run it.

It also doesn't see problems with chars, or wrong lines but that is related to: PowerShell/PSScriptAnalyzer#1089 and

PowerShell/PSScriptAnalyzer#981 still I would expect PSSA to pick this up? Or I have wrong expectancy on this?

[TylerLeonhardt]

So I think this is a combination of issues.

1. that you're not getting results beck from PSScriptAnalyzer fast enough - dupe of Error/warning detection is randomly broken #1232

2. that you'd like a feature from VSCode to split the bottom pane where you could have Problems next to, say, the Terminal.

@PrzemyslawKlys would you mind opening an issue on VSCode for that feature request?

Is it reasonable to close this as a dupe?

[PrzemyslawKlys]

Sure. I'll open it up there. Actually, I often don't get "problems" at all or get them very late. But it's most likely related to all other issues I reported with relative vs absolute path and for some reason, it's displaying it late or never.

[PrzemyslawKlys]

Like...

So many problems, and complains... that are not there anymore. I can press F5 and it will tell me there are no errors, yet VS Code claims there are 6 problems :-) including critical ones...