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
These functions work for @click.option types, which have a key and a value. But for @click.argument types, there is no key (e.g. in your CLI command, you don't say --my-argument=5, you would just write 5, because @click.argument types are positional. It appears this was not accounted for anywhere in workflow-core, but I remember this working before with chime-frb-api.
As a result, the func.main(args=arguments, standalone_mode=False) call in lifecycle/execute.py fails because, say if you have a @click.argument called ra and it's given a value of 100, the args here will include ra=100 but it should just be 100; it will produce an error saying ra=100 is not a valid float value.
The text was updated successfully, but these errors were encountered:
These functions work for @click.option types, which have a key and a value. But for @click.argument types, there is no key (e.g. in your CLI command, you don't say
--my-argument=5
, you would just write5
, because @click.argument types are positional. It appears this was not accounted for anywhere in workflow-core, but I remember this working before with chime-frb-api.As a result, the
func.main(args=arguments, standalone_mode=False)
call in lifecycle/execute.py fails because, say if you have a @click.argument called ra and it's given a value of 100, theargs
here will includera=100
but it should just be100
; it will produce an error sayingra=100 is not a valid float value
.The text was updated successfully, but these errors were encountered: