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 }}
This repository has been archived by the owner on Mar 16, 2024. It is now read-only.
@cjellick I am able to set boolean flag to "true" when it is passed with "=" like --newApp=false in the arg list.
This issue is seen only when it is passed with out "=" like --newApp false in the arg list.
In the example provided in the above issue ,
acorn run -n mytest -f Acornfilebool -- --newApp=false --newtext nnupdate --oldtext ooupdate works as expected.
The issue is seen only when we launch the app as follows without "=" for the boolean args acorn run -n mytest -f Acornfilebool -- --newApp false --newtext nnupdate --oldtext ooupdate
This is a limitation of the flag parsing lib we use. See: spf13/cobra#613
Not super high priority, but im tempted to go as far a dropping use of the actual bool flag and have our own string-based bool-ish flag that behaves more predictably
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
acorn version v0.8.0-80-g635ea0a6+635ea0a6
Steps to reproduce the problem:
newApp
-acorn run -n mytest . --newApp false --newtext nnupdate --oldtext ooupdate
Acornfile used:
This results in
newApp
being set totrue
Spec for the app shows
newApp
set to true even when "false" was passed.Possibly related to type not shown for boolean args in
acorn help
The text was updated successfully, but these errors were encountered: