Fallout-build/Fallout

Rename legacy s_-prefixed private fields to camelCase and enforce the rule

已關閉

#481 建立於 2026年7月12日

 (3 則留言) (0 個反應) (0 位負責人)C# (16 個分叉)github user discovery
enhancementgood first issuetarget/backlog

倉庫指標

星標
 (125 顆星)
PR 合併指標
 (平均合併 2天 15小時) (30 天內合併 63 個 PR)

描述

Problem

.editorconfig:73-85 mandates camelCase private fields (no _/m_/g_/s_ prefix, per CSharpGuidelines AV1702/AV1705) but keeps severity = suggestion because ~35 legacy s_-prefixed identifiers across ~34 files still violate it (e.g. Telemetry.s_confirmedVersion). The convention is documented but not compiler-enforced, so new violations slip in. Surfaced in #451 review.

Outcome

No prefixed private fields remain; the naming rule is warning, so new violations fail the build.

Acceptance criteria

  • All s_/_/m_/g_-prefixed private fields in src/**/*.cs renamed to camelCase
  • dotnet_naming_rule.private_fields_should_be_camel_case.severity bumped suggestionwarning (.editorconfig:78)
  • Build green with no new naming warnings

Notes

Mechanical rename; exclude generated code. Low priority.

貢獻者指南