DEV Community

Discussion on: Feature Management in .NET

Collapse
 
davinceleecode profile image
davinceleecode

If you don't mind how to handle features that are dependent and already running in production, what happens if you disable them?

Collapse
 
vimaltwit profile image
Vimal

You mean like features that are dependent on other features? Could you elaborate your scenarios so that I could help please?

Collapse
 
davinceleecode profile image
davinceleecode

Yeah, exactly.
I meant situations where a feature depends on another one that's already running in production. For example, if I disable the main feature via a feature flag, but some parts of the app still rely on it, how should I handle that safely? Should I add extra checks in dependent features or group them under a shared flag?

Thread Thread
 
vimaltwit profile image
Vimal • Edited

Interesting scenario I must say!! This mostly depends on your use case, but yes one solution would be to add extra checks in dependent features. A Better solution - you could refactor the shared functionality and reduce coupling. This way you could use feature flags without any hierarchy or additional checks. Does that make sense?