Consider adding IgnoresAccessChecksTo("Unsupported")
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.4k
- Forks
- 835
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes you need a little tweak so some internal implementation which hasn't been made public API surface because a mainstream enough scenario couldn't be found to support it.
An (little known) escape hatch to avoid visibility checks is available that can unlock very specific and niche cases, provided the user is very clear on the risk of internals changing without notice and their code not being supported in any way.
Contributor guide
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
The issue names no files, tests, or entry points. Start by reading the linked Roslyn article and searching the repository for assembly visibility or related configuration. Done means the requested escape hatch has a defined supported scope, documented risks, and suitable verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100