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
Is your feature request related to a problem? Please describe.
The current CLI calls can get confusing, especially with a lot of options (some of them being listed as optional by argparse but being required) and when options are linked to a subcommand and must be placed after the keyword (e.g. child-project metrics . results.csv --vtc vtc aclew --recordings recs.csv will not work because --recordings should be before aclew (linked to metrics subcommand) and --vtc should be after aclew (because linked to aclew subcommand)
Describe the solution you'd like
More thinking needed,
could be technically hard to release the placement constraints
could lead to conflicts to remove placement constraints (same options for subcommands)
could let go of the use of argparse (because forces a certain --help format)
Is your feature request related to a problem? Please describe.
The current CLI calls can get confusing, especially with a lot of options (some of them being listed as optional by argparse but being required) and when options are linked to a subcommand and must be placed after the keyword (e.g.
child-project metrics . results.csv --vtc vtc aclew --recordings recs.csv
will not work because--recordings
should be beforeaclew
(linked tometrics subcommand
) and--vtc
should be afteraclew
(because linked toaclew
subcommand)Describe the solution you'd like
More thinking needed,
--help
format)The text was updated successfully, but these errors were encountered: