Skip to content
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

Closed
DustinCampbell opened this issue Feb 13, 2017 · 6 comments
Closed

Problems list dominated by unused usings #1231

DustinCampbell opened this issue Feb 13, 2017 · 6 comments
Assignees
Milestone

Comments

@DustinCampbell
Copy link
Member

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?

image

Copied from original issue: OmniSharp/omnisharp-roslyn#769

@DustinCampbell
Copy link
Member Author

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.

@davidfowl
Copy link
Member

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.

@DustinCampbell DustinCampbell added this to the 1.8 milestone Feb 13, 2017
@DustinCampbell
Copy link
Member Author

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.

@davidfowl
Copy link
Member

Keep the code fix but remove the info 😄

@skryshi
Copy link

skryshi commented Mar 13, 2017

I was so looking forward to this in 1.8... (

@DustinCampbell
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants