You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Custom Action - Input Control (Checkbox) : Add 'Unchecked Value' and provide sensible defaults #1482
When creating/editing a Checkbox input-control for a Custom Action, we should be able to specify a Unchecked Value, just like the Checked Value already present.
Also, these two fields of Checked Value / Unchecked Value should start pre-filled with sensible defaults, like true / false, 1 / 0 (or similar).
Motivation: Currently the input-variable is expanded to an empty string by default, when the checkbox is unchecked. This makes it a bit error-prone, since this argument will then be skipped and will break the order of arguments, unless it is enclosed in quotes on the resulting command-line. Also, the Checked Value is currently empty by default, which means there will be no distinction between checked/unchecked if we just create a checkbox without touching this field. Adding the Unchecked Value as a modifiable field, and providing non-empty defaults for both of these fields, would improve its ease-of-use (while still supporting empty-string variants if desired)...
(The help-text below the Checked / Unchecked Value fields should be changed to say "... these values ...".)
CheckBox is designed only being used as a toggle of its underline Checked Value, which will change the way the external tool/script behaves.
For example:
git fetch will not overrides the local ref by default if it is mismatched with remote one
When --force is enabled, git fetch command will disable this check
So, in my opinion, a simple --some-swith-option is really better than --some-switch-option=true|fase, since for switch-type-options, the program always needs to implement a default behavior.
Activity
love-linger commentedon Jul 1, 2025
CheckBoxis designed only being used as a toggle of its underlineChecked Value, which will change the way the external tool/script behaves.For example:
git fetchwill not overrides the local ref by default if it is mismatched with remote one--forceis enabled,git fetchcommand will disable this checkSo, in my opinion, a simple
--some-swith-optionis really better than--some-switch-option=true|fase, since for switch-type-options, the program always needs to implement a default behavior.love-linger commentedon Jul 1, 2025
And when a commandline option supports different values, such as
--some-option=1|2|3, I think an extraCombBoxinput element is better thanCheckBoxfeature: supports to use `ComboBox` input control in cutom actions (#…
goran-w commentedon Jul 1, 2025
Ah, I see - makes sense!
Great new feature, thanks!