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
Switch back to the source file and see the diagnostics/squiggles on M
Expected Behavior:
IDE0051 warning in error list and a squiggle for the same in the editor
Actual Behavior:
IDE0051 is still a message and there is no squiggle.
Keep editing the source file, say renaming M to M2, renaming the containing type, adding more code, etc.
Expected Behavior:
.editorconfig dotnet_diagnostic should take effect at least after doing some source code edits.
Actual Behavior:
IDE0051 is still a message and there is no squiggle. The diagnostic correctly gets updated to say M2 instead of M, so diagnostics are not stale - just the fact that new editorconfig settings are not being applied at all. Only way to get these applied are to close and re-open/reload the project.
The text was updated successfully, but these errors were encountered:
I verified that issue started happening after #44331. It does not repro on 16.8 P2 builds prior to that change getting merged. @jasonmalinowski can you take a look? I'll try to work on an integration test to repro this behavior.
Version Used: Latest 16.8 P2 dogfood build
Steps to Reproduce:
IDE0051
reported forM
:M
Expected Behavior:
IDE0051 warning in error list and a squiggle for the same in the editor
Actual Behavior:
IDE0051 is still a message and there is no squiggle.
M
toM2
, renaming the containing type, adding more code, etc.Expected Behavior:
.editorconfig
dotnet_diagnostic
should take effect at least after doing some source code edits.Actual Behavior:
IDE0051 is still a message and there is no squiggle. The diagnostic correctly gets updated to say
M2
instead ofM
, so diagnostics are not stale - just the fact that new editorconfig settings are not being applied at all. Only way to get these applied are to close and re-open/reload the project.The text was updated successfully, but these errors were encountered: