FeatureToggle icon indicating copy to clipboard operation
FeatureToggle copied to clipboard

Published 20 hours ago • verified publisher icon jason-roberts

FeatureToggle V5 Roadmap

Open jason-roberts opened this issue 7 years ago • 6 comments

This is an overview of the potential themes for v5

  • Move to "pure" .net standard implementation
  • Move to .NET standard 2
  • Simplify configuration (try and have a single method regardless of platform: UWP, Core, Full. etc)
  • Simplify solution in visual studio (e.g. remove multi-targeting and have a single .NET standard class lib)
  • Maybe take the opportunity for a major release to re-examine the architecture of providers and how toggles are read

jason-roberts avatar Feb 15 '18 04:02 jason-roberts

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.

mikanyg avatar Apr 21 '18 21:04 mikanyg

Thanks @mikanyg any thoughts gladly accepted :)

jason-roberts avatar May 14 '18 04:05 jason-roberts

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: The SqlProvider should be greatly enhanced. It could support other than the boolean flag and the Sql should not go in the config by default. The RavenDb provider and even the JsonEnabled could be moved to seperate Provider packages. Kinda like Serilog has many sink packages.

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.

mikanyg avatar May 16 '18 19:05 mikanyg

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.

jason-roberts avatar Jun 01 '18 02:06 jason-roberts

Are you still actively maintaining this project, @jason-roberts ? Looking for a library to use for a client.

ardalis avatar Apr 09 '19 15:04 ardalis

bump

ardalis avatar Apr 12 '19 15:04 ardalis