check-naming

To enforce C# naming conventions during code reviews, audit the file or selection to validate identifiers against Microsoft and project standards. This checks types, members, and fields for PascalCase, proper prefixes, and async suffixes, reporting violations with suggested fixes.

The C# naming rules supported include Type Naming, Interfaces, Records, Structs, Enums, Delegates, Members, Fields, Async Naming, and generic type parameters. It checks for PascalCase, proper interface prefixes, descriptive nouns, and async method suffixes.

Yes, you can validate private field naming conventions and async method suffixes in C#. The checker validates member naming for methods, properties, parameters, and private fields, ensuring async methods are correctly suffixed according to project standards.

Yes, this C# naming linter aligns with Microsoft coding standards. It enforces Microsoft-aligned C# naming conventions across types, members, and fields, ensuring identifiers follow PascalCase, proper prefixes, and descriptive nouns.

To validate identifiers when onboarding to a new C# codebase, audit the current files or selections against the project naming standards. This reduces confusion and improves maintainability by reporting violations with clear suggested fixes.

The best way to audit C# records and structs for naming violations is to run a validation check on the selected files. It checks Type Naming for classes, interfaces, records, structs, and enums for PascalCase and proper prefixes, providing clear violation reporting.