Uh oh!
There was an error while loading. Please reload this page.
Commit ba5aa10
Fix resolveBooleanFlag dropping explicit false values
Option.filter(flag, Boolean) converts Some(false) to None because
Boolean(false) is false. This caused explicit --no-signed (and similar
--no-* flags) to be silently ignored when the corresponding env var
was set to true. Remove the filter so explicit CLI false values take
precedence over environment defaults.
Co-authored-by: Julius Marminge <juliusmarminge@users.noreply.github.com>1 parent 8c2797a commit ba5aa10
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
139 | 139 | | |
140 | 140 | | |
141 | 141 | | |
142 | | - | |
| 142 | + | |
143 | 143 | | |
144 | 144 | | |
145 | 145 | | |
| |||
0 commit comments