microsoft / microsoft/FeatureManagement-Dotnet
Any plans on creating an abstraction package?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 129
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
Many of the Microsoft.Extensions packages comes with an abstraction package containing the fundamental interfaces for a component. This can be a lifesaver when trying to untangle dependency graphs/verison constraints in larger projects.
With this in mind - and in the light of the dependencies that the feature toggle package have taken - are there any plans to extract IFeatureManager, IFeatureFilter et. al. into a abstraction package?
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 current FeatureManagement package and the Microsoft.Extensions pattern of separate abstraction packages, focusing on IFeatureManager and IFeatureFilter. Done would mean defining and agreeing on an abstraction package boundary that reduces dependency and version-constraint issues; the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100