abpframework / abpframework/abp
Implementing Feature Toggle
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14.4k
- Forks
- 3.7k
- Avg merge
- 15h 32m
- Merged PRs (30d)
- 106
Description
What is the recommended approach to do Feature Toggle implementation in Abp?
Keep in mind that I might have a temporary feature toggles that is available in Release 1 and I might remove it in Release 2 or 3.
Also I have some business Feature toggles, so I might have a feature which requested by two clients; But I want to ship it with Logic A for the 1st client and with Logic B for 2nd client (Looks like it's a DI/IoC thing). But I would like to hear from you?
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
The issue names no files, tests, or entry points; begin by surveying ABP's existing feature-management and dependency-injection guidance. Done would require a maintainer-approved approach covering temporary release toggles and client-specific behavior before implementation can be scoped.
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
- Needs clarification
- Newbie friendliness
- 25/100