Browse Source

Report field naming violations as suggestions

The naming rules have been warnings since they were introduced; they are
advisory conventions rather than build gates, and the noise they add to
every file listing outweighs their value.

Assisted-by: Claude:claude-opus-5[1m]:Claude Code
pull/4087/head
Siegfried Pammer 2 weeks ago
parent
commit
08f08136b3
  1. 4
      .editorconfig

4
.editorconfig

@ -144,11 +144,11 @@ dotnet_naming_symbols.private_fields_symbols.applicable_kinds = field
# Naming rules: # Naming rules:
# all non-private fields are pascal case # all non-private fields are pascal case
dotnet_naming_rule.fields_rule.severity = warning dotnet_naming_rule.fields_rule.severity = suggestion
dotnet_naming_rule.fields_rule.style = upper_camel_case_style dotnet_naming_rule.fields_rule.style = upper_camel_case_style
dotnet_naming_rule.fields_rule.symbols = fields_symbols dotnet_naming_rule.fields_rule.symbols = fields_symbols
# all private fields are camel case # all private fields are camel case
dotnet_naming_rule.private_fields_rule.severity = warning dotnet_naming_rule.private_fields_rule.severity = suggestion
dotnet_naming_rule.private_fields_rule.style = lower_camel_case_style dotnet_naming_rule.private_fields_rule.style = lower_camel_case_style
dotnet_naming_rule.private_fields_rule.symbols = private_fields_symbols dotnet_naming_rule.private_fields_rule.symbols = private_fields_symbols

Loading…
Cancel
Save