For Private Const we want the rule to allow: <div class="highlight highlight-sourc

Have checked the configuration and both <a href="https://github.com/DotNetAnalyzers/St

What about turning on <a href="https://github.com/DotNetAnalyzers/StyleCopAnalyzers/bl

What about turning on <a href="https://github.com/DotNetAnalyzers/StyleCo

The code for SX1309 seems to suggest otherwise: <div class="Box

Have checked the configuration and both <a href="https://github.com/DotNe

What about using <a href="https://learn.microsoft.com/en-us/dotnet/fundamentals/code-a

SA1303: Can we configure this to warn if the 1st char is _ about stylecopanalyzers HOT 6 OPEN

TickettEnterprises commented on July 3, 2024

SA1303: Can we configure this to warn if the 1st char is _

from stylecopanalyzers.

Comments (6)

TickettEnterprises commented on July 3, 2024 1

Have checked the configuration and both SA1300 and SX1309 are set to error.

However no error is shown for:

private const string _testing = "";

Only shown for

private const string _testing = "";
private string testing = "";

from stylecopanalyzers.

sharwell commented on July 3, 2024

What about turning on SA1300 and SX1309?

from stylecopanalyzers.

TickettEnterprises commented on July 3, 2024

What about turning on SA1300 and SX1309?

This would not work because what we are trying to achieve is:

Private const use PascalCase starting with capital.
But we still want non const privates to start with a _

Turning on SX1309 would mean all fields need to start with _.

from stylecopanalyzers.

sharwell commented on July 3, 2024

The code for SX1309 seems to suggest otherwise:

StyleCopAnalyzers/StyleCop.Analyzers/StyleCop.Analyzers/NamingRules/SX1309FieldNamesMustBeginWithUnderscore.cs

Lines 68 to 71 in f5f4ca9

    
           case SyntaxKind.StaticKeyword: 
        
           case SyntaxKind.ConstKeyword: 
        
               // This analyzer only looks at instance fields. 
        
               return;

from stylecopanalyzers.

TickettEnterprises commented on July 3, 2024

Have checked the configuration and both SA1300 and SX1309 are set to error.

However no error is shown for:
private const string _testing = "";
Only shown for
private const string _testing = "";
private string testing = "";

This is not the intended result, as outlined we want to enforce private const to start with Cap and not _.
And private to start with a _

from stylecopanalyzers.

CruseCtrl commented on July 3, 2024

What about using IDE1006 along with this in your .editorconfig:

dotnet_naming_rule.private_constant_fields_should_be_pascalcase.severity = warning
dotnet_naming_rule.private_constant_fields_should_be_pascalcase.symbols = private_constant_fields
dotnet_naming_rule.private_constant_fields_should_be_pascalcase.style = pascalcase

dotnet_naming_symbols.private_constant_fields.applicable_kinds = field
dotnet_naming_symbols.private_constant_fields.applicable_accessibilities = private, protected, protected_internal, private_protected
dotnet_naming_symbols.private_constant_fields.required_modifiers = const

dotnet_naming_style.pascalcase.required_prefix =
dotnet_naming_style.pascalcase.required_suffix =
dotnet_naming_style.pascalcase.word_separator =
dotnet_naming_style.pascalcase.capitalization = pascal_case

That seems to do what you want

(I'm using this .editorconfig file, which was made by one of my colleages)

from stylecopanalyzers.

Recommend Projects