-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Naming style for static members contradicts with the page "Names of Type Members" #30642
Comments
This is an area we should look at more holistically. In general, our docs follow the dotnet/runtime coding style. We should update these articles to match that, and point liberally to the editorconfig section of the Visual Studio docs to enable each team to enforce their preferences. |
Sounds good, thanks so much. I think clarifying this consistently would be good. Unfortunately some of these conventions also don't align with StyleCop defaults which makes it a little more confusing for someone who isn't as familiar with the language. Kindest Regards |
Fixes dotnet#30626: Clarify (again) that these are our guidelines, not yours. Point out that it's not the VS default, but a configuration option. Fixes dotnet#30642: Again, our style. Fixes dotnet#30799: Change constant style from ALL_CAPS to PascalCase to match runtime repo. Fixes dotnet#33959: Update variable names so delegate types are PascalCased and instances of a delegate are camelCase. Add clarifying text for the same.
This page suggests using a
s_
prefix for static members yet the Names of Type Members docs specifically say:Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Associated WorkItem - 123087
The text was updated successfully, but these errors were encountered: