-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FeatureToggle V5 Roadmap #155
Comments
If you are going to change the provider model, I'm very interesting in your future thoughts. I have created 3 provider so far FeatureToggle.Azure and have some opinions on the matter. |
Thanks @mikanyg any thoughts gladly accepted :) |
It would be nice to know if any breaking changes was planned. But in general I think that having a good provider model is a way to have even more provider projects/packages being developed. Some thoughts on the existing providers: Finally if some management web ui could interact with the flags via the centralized providers (not the ones in config files) would be really cool. Inspired from the way HangFire (Background Job Scheduler) has both core packages, providers and a management UI package. |
Thanks @mikanyg - I appreciate all those suggestions. This library embraces semantic version so version 5 will be allowed breaking changes, I thought about the separate provider packages thing before so any suggestions on how to implement this are welcome :) I'm also happy to talk about modifying the SQL stuff. One thing that's always been out of scope has been the management of updating toggles (e.g. web UI). This is something that I'm open to in the future but probably a good idea to focus on v5 first and then have another think about it. |
Are you still actively maintaining this project, @jason-roberts ? Looking for a library to use for a client. |
bump |
This is an overview of the potential themes for v5
The text was updated successfully, but these errors were encountered: