Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Hidden diagnostics are not displayed in the problems panel
See original GitHub issueIssue Description
Maybe after this https://github.com/OmniSharp/omnisharp-vscode/pull/2873 , the csharp.suppressHiddenDiagnostics option does nothing.
Environment data
C# Extension version: 1.20.0 , v1.21.0-beta1 , v1.21.0-beta2
Steps to reproduce
"csharp.suppressHiddenDiagnostics": false or "csharp.suppressHiddenDiagnostics": true
Expected behavior
Hidden diagnostics should be displayed in the problems panel.
Actual behavior
Hidden diagnostics are not displayed in the problems panel.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
IDE information diagnostics displayed in the VS Code ... - GitHub
IDE information diagnostics displayed in the VS Code problems pane do not surface via dotnet build #60620 · Comments · Restating the problem....
Read more >How to Access the Secret Hardware Diagnostic Menu on Your ...
Launching diagnostics is easy: just open your Phone app and type *#0*#. The phone should immediately open the diagnostic menu, shown below.
Read more >Samsung washing machine diagnostic mode How ... - YouTube
How to enter diagnostic test mode on a Samsung washing machine fault findingthis video can be used on most Series 5 ecobubble, QuickDrive, ......
Read more >Diagnostics, feedback, and privacy in Windows
Microsoft uses diagnostic data to keep Windows secure and up to date, troubleshoot problems, and make product improvements as described in more detail...
Read more >How to Test Your Samsung Phone by Using Secret Code *#0
From there, enter *#0*# using the dial pad, and the phone will immediately go into its secret diagnostic mode. Note that the process...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
They were modified work so that
csharp.suppressHiddenDiagnosticscontrols will hidden diagnostic be hidden or hints instead. Hints are visible as small dots in editor. However they are not visible in problem panel.suppressHiddenDiagnosticswas actually bit misleading, it didn’t control visibility of issues but instead changed their severity in place from hidden -> information. There is mismatch between roslyn - vscode diagnostics since vscode doesn’t have hidden diagnostic level at all.As far as i know from PR/code history origin for this flag was workaround issue with unused usings where they were not visible since only analysis for them without analyzers had hidden severity. Back then there were no way to control how diagnostics behaved or what their severity was.
You can have fine grained control of issue severity and visibility with
.rulesetfiles which are now supported in bot analyzers enabled and disabled.Can you solve your use case with .rulesets? If not can you describe use case?
I will admit that this behaviour confused me too. My expectation would be that such errors would appear in the Problems panel after disabling
csharp.suppressHiddenDiagnostics. It would be awesome to see a setting that allowed this to be the case without editing the ruleset or .editorconfig file.