Check for defaults loosely to allow falsy values

Open waiteb3 opened this issue 8 years ago • 1 comments

This small landmine caught me when I set a env-var default to false, rather than "false", for a flag. This would also cause issues for 0 or other falsey values.

Aug 15 '17 13:08 waiteb3

Coverage remained the same at 97.527% when pulling 012da115544b4c777638cadb952e90d92e680bd8 on waiteb3:patch-1 into e61c962c05eb44478f26aa1a9a3d45dce27d6b0f on inxilpro:master.

Aug 15 '17 14:08 coveralls