I fully agree that we need a standard way of doing boolean FeatureFlags. I believe the lack of it indicates that Feature Flags are incomplete, since enabling/disabling features was described as key functionality.
But I think using empty/non-empty to indicate boolean is pretty gross.
I fully agree that we need a standard way of doing boolean FeatureFlags. I believe the lack of it indicates that Feature Flags are incomplete, since enabling/disabling features was described as key functionality.
But I think using empty/non-empty to indicate boolean is pretty gross.