microsoft / microsoft/FeatureManagement-Dotnet
Pass FeatureFilterEvaluationContext in ITargetingContextAccessor implementation
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 129
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
While using the library I ran into scenarios where the targeting context can be different for different features and having the feature definition allows the implementation to take decision based on feature being evaluated.
Please consider this as a new feature in your upcoming release.
Thanks!
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 locating the ITargetingContextAccessor implementation and existing uses of FeatureFilterEvaluationContext. Determine how the feature definition should be supplied for each evaluated feature; done means implementations can make feature-specific targeting decisions. The issue does not name tests or files, so inspect existing coverage before changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100