Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Should we talk about non-public static fields starting with s_ ???

Open
  • Is something wrong?
#760 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
documentation

Research direction

Start by reviewing the linked .NET naming-rules guidance and the surrounding Essential C# documentation context. Determine whether non-public static fields using the s_camelCase convention should be discussed; this issue is done when the documentation decision and any resulting scope are recorded.

Written by the indexing model from the issue text.

Description

Non-public static fields are s_camelCase.

https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/naming-rules#example-const-modifier-includes-static-and-readonly

Dominant language
C#
Stars
419
Forks
173
Avg merge
3m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntelliTect/EssentialCSharp

All issues in IntelliTect/EssentialCSharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.