ALL_CAPS private const field bypasses the rules #53
-
|
Hi, I'm having a play with editorConfig and applying the PascalCase rule for private const field like
but I do not get a warning, I assume the following section should be dealing with this? All constant fields must be PascalCasehttps://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1303.mddotnet_naming_symbols.stylecop_constant_fields_group.applicable_accessibilities = public, internal, protected_internal, protected, private_protected, private |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Just tested this and I can see that VS 16.9 doesn't show a warning. This used to work but not sure when it stopped working. I tried a blank .editorconfig file with nothing but these rules in it and I got nothing. Just ran through the docs on these custom rules again and it seems like we are doing the right thing. We should probably check for an issue or raise one in the Roslyn GitHub repo. https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/naming-rules |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for such a quick response, I have duplicated into the project |
Beta Was this translation helpful? Give feedback.
Just tested this and I can see that VS 16.9 doesn't show a warning. This used to work but not sure when it stopped working. I tried a blank .editorconfig file with nothing but these rules in it and I got nothing.
Just ran through the docs on these custom rules again and it seems like we are doing the right thing. We should probably check for an issue or raise one in the Roslyn GitHub repo.
https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/naming-rules