DEV Community

loading...

The poor man's feature flag

tinydevops profile image Jonathan Hall Originally published at jhall.io on ・1 min read

I recently had a chat with a developer whose team had recently made the switch from GitFlow to trunk-based development. He observed that long-lived features were painful in trunk-based development, due to the lack of feature flags.

While there are many great feature flag frameworks and tools out there, you don’t need to wait for your team to implement one to start using feature flags. You can start today with the poor man’s feature flag:

if (false) {
Enter fullscreen mode Exit fullscreen mode

Yeah, that’s it.

Wrap your new, incomplete feature in a simple if (false) conditional, and merge it into master as normal.

Any unit tests you’ve written will still run and execute your new code—it just won’t be exposed in production builds. Perfect!

When you’re working on it locally, just change if (false) to if (true), and hack away. And when the feature is finally complete, delete the conditional entirely.


If you found this message interesting, I expand on the topic of feature flags in my free What is Continuous Integration email series.

Discussion (0)

pic
Editor guide