microsoft / microsoft/FeatureManagement-Dotnet
Consider the ability to allocate variants based on custom filters
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 129
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
Variants are going to be a huge boon to this library and I'm excited to leverage them. I often find myself creating custom filters that evaluate based on the application state rather than the traditional user centric targeting scenarios. It would be great if we could allocate variants based on these filters. Perhaps something like:
"FeatureManagement":
{
"MyVariantFeatureFlag":
{
"Allocation": {
"DefaultWhenEnabled": "Small",
"AllocatedFor": [
{
"Name": "CustomFilter",
"Parameters": {
"SomeParam": "SomeValue"
},
"Variant": "Big"
}
]
},
"Variants": [
{
"Name": "Big"
},
{
"Name": "Small"
}
]
}
}
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 by reviewing the variant allocation and custom-filter behavior described in issue #460, then trace the existing variant and filter entry points in the repository. Define how the shown FeatureManagement configuration should select Big versus Small for application-state filters, and add coverage for the requested configuration and selection behavior.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100