open-feature / open-feature/dotnet-sdk
[FEATURE] Domain configuration should have a fluent, domain-first API
Open
Nobody has claimed this yet.
area: dependency-injection
type: feat
- Dominant language
- C#
- Stars
- 138
- Forks
- 27
- Avg merge
- 13h 42m
- Merged PRs (30d)
- 12
Description
Requirements
Today, domain-related configuration (context, provider) is spread across separate calls, which can be fragmented and error-prone in multi-domain setups. Discuss a fluent AddDomain("name", cfg => { ... }) style API where all domain-level concerns are configured in one place.
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
Review the current domain-related context and provider configuration entry points in the .NET SDK. Compare them with the proposed AddDomain("name", cfg => { ... }) shape and identify the domain-level concerns it should contain. Done means an agreed, implementable API design for multi-domain configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100