-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems list dominated by unused usings #1231
Comments
This is a duplicate of #315 but I'm going to keep it on the backlog. Sadly, there is no way to downgrade a diagnostic such that it's completely hidden in the Problems window today. We could make it a "hint", but that only hides the squiggle in the editor and leaves it in the Problems window, which isn't what we want. I have microsoft/vscode#20219 open to get an API that'll allow us to have a better more VS-like experience here. |
Maybe we can just remove them as problems for now in general? It's just noise at this point. When we get the new API then we can improve the experience all up. |
Maybe, I'm not super-keen on the user experience of having no presentation in the editor at all for this remove unnecessary usings. That said, maybe you're right and it's worth it to hide for now and bring back in it's full glory later. 😄 I'll take a look for 1.8. |
Keep the code fix but remove the info 😄 |
I was so looking forward to this in 1.8... ( |
Sorry about this. I had to slip this one to get 1.8 out for some important debugger changes. Fixing this is on my list after restoring test support for csproj .NET Core projects. |
From @davidfowl on February 12, 2017 18:13
Makes it hard to see real problems. Can we downgrade this thing so it doesn't show up by default in the list of problems?
Copied from original issue: OmniSharp/omnisharp-roslyn#769
The text was updated successfully, but these errors were encountered: