open-feature / open-feature/dotnet-sdk
[FEATURE] IFeatureClient scoped lifetime prevents use in singleton services
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 138
- Forks
- 27
- Avg merge
- 13h 42m
- Merged PRs (30d)
- 12
Description
Requirements
Scoped registration forces consumers to manually create DI scopes when using IFeatureClient from singletons, adding boilerplate and increasing misuse risk. Discuss splitting into IFeatureClient (singleton) and IFeatureClientSnapshot (scoped), similar to IFeatureManager / IFeatureManagerSnapshot in Microsoft Feature Management.
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
Start by reviewing the existing IFeatureClient registration and interface usage, then compare the IFeatureManager and IFeatureManagerSnapshot pattern named in the issue. Define the singleton and scoped lifetime expectations, identify affected consumers and tests, and confirm the design before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100