Why so much private members available?
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Related to:
It is not clear wich stuff should be accessed from wich, occasional developer may be tempted to access internals, may you consider to re-evaluate what should be private and protected (possibly augmenting the incapsulation)?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the related Stack Overflow question, then review the websocket-sharp members implicated in the server-close behavior and identify which public, protected, and private boundaries are being questioned. The issue does not name files or tests, and completion requires an agreed encapsulation policy and scope before any visibility changes can be considered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100