Software dev with experience in Windows, .NET, web dev, APIs, .NET Core, Razor Pages, and ReactJS. I love exploring new tech and building modern solutions.
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?
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?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You mean like features that are dependent on other features? Could you elaborate your scenarios so that I could help please?
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?
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?