3 ms·
> Doesn't this throw out some of the point of feature flags? Not if you're using feature flags as an alternative to branching, nor if your feature flag is inte
by dahart 9y ago
> Doesn't this throw out some of the point of feature flags?
Not if you're using feature flags as an alternative to branching, nor if your feature flag is intentionally temporary. A branch is temporary, and merging the branch doesn't eliminate the point of branches, right?
For performance toggles you want to keep and use, then definitely just keep those.
> Feature toggles implemented through conditional logic seems like an anti-pattern to me. Developers make mistakes, and it's very easy to forget to wrap work around the necessary toggles
This is a valid concern generally, but in my experience doesn't detract much from the reasons to use feature toggles. In particular, the good examples you brought up (performance features & API feature toggles) you can't have without conditional logic, so there isn't any choice or alternative, right?
> It seems to me like a better pattern would be to feature-toggle on an API level
That's a good idea when the feature in question is an API feature. Are you a backend kind of person? ;) Lots of features are frontend, lots of features are full-stack. It all just depends on which feature, but generally speaking having API level feature toggles in your toolbelt is a great idea.