You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I know, code analyzer rules can be suppressed in many ways incl. editorconfig (doesn't seem to work here). The documentation of vs talks about the fact that there is a code action for suppressing code analyser rules, however it does not show in vscode when invoking code action list for rule violations. I got the info that this is implemented in roslyn, so is not vs specific.
The text was updated successfully, but these errors were encountered:
however, the way to control analyzer severity via editorconfig is currently not supported (this is a fairly new feature in Roslyn that only came in VS 16.3).
it is tracked by OmniSharp/omnisharp-roslyn#1657 so I will close this as duplicate.
As a workaround you can still use rulesets and those will be supported in OmniSharp.
From what I know, code analyzer rules can be suppressed in many ways incl. editorconfig (doesn't seem to work here). The documentation of vs talks about the fact that there is a code action for suppressing code analyser rules, however it does not show in vscode when invoking code action list for rule violations. I got the info that this is implemented in roslyn, so is not vs specific.
The text was updated successfully, but these errors were encountered: