Closed kshitij-k-osmosys closed 3 months ago
The recent update introduces refined naming conventions for C# code within .NET projects, focusing on private and static fields. By defining an underscored naming style, these changes aim to promote uniformity and clarity across the codebase, ensuring that private and static fields are easily identifiable and consistently named, enhancing readability and maintainability.
Files | Summary |
---|---|
coding-standards/.../dotnet.md |
Updated naming rules and styles for private and static fields, introducing an underscored naming style. |
🐇✨
In the realm of code, where rules align,
A rabbit hopped, leaving marks behind.
"For fields both static and unseen,
Let underscores guide the scene."
With every hop, a change is sown,
In .NET lands, a standard's grown.
🌱🚀
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Description
Enforce private variable naming conventions of camelCased name preceeded by underscore
_
Ex._privateVariableName
Issue URL: https://github.com/OsmosysSoftware/dev-standards/issues/53
Screenshots
Dotnet Core 8.0
Dotnet framework 4.5.2
Sources
Microsoft documentation: Private instance fields start with an underscore (_) and the remaining text is camelCased.
Microsoft editorconfig rule
Summary by CodeRabbit