env_config: deprecate setting boolean vars to falsy values #18408
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
brew style
with your changes locally?brew typecheck
with your changes locally?brew tests
with your changes locally?The way we handle boolean environment variables is a bit unfortunate.
For example, setting
HOMEBREW_EVAL_ALL=false
actually enablesHOMEBREW_EVAL_ALL
.Let's fix this by deprecating setting boolean environment variables to
common false-y values (
false
,0
,nil
,no
, andoff
) so that wecan later ignore these false-y values when reading boolean environment
variables.
Note: I haven't commented out
odeprecated
because I meant to target the PR branch at #18388, but that seems to have merged just before I pushed this.