Expected behaviour:
When working with the CLI arguments that are not allowed at the current position should throw an error.
flexget execute --tasks super_duper_task --test should not be allowed as --test pertains to flexget not to the execute action.
Actual behaviour:
flexget execute --tasks super_duper_task --test is allowed (--test being at the wrong position) and doesn't throw an error.
In this case the test DB is not created which isn't optimal if you want to test things out...
Steps to reproduce:
- Run
flexget execute --tasks super_duper_task --test
- (╯°□°）╯︵ ┻━┻ because you just destroyed your database with the
super_duper_task
- Should have known to put
--test right after flexget
Additional information:
- Flexget Version: 2.3.25
- Python Version: 2.7.12
Expected behaviour:
When working with the CLI arguments that are not allowed at the current position should throw an error.
flexget execute --tasks super_duper_task --testshould not be allowed as--testpertains toflexgetnot to theexecuteaction.Actual behaviour:
flexget execute --tasks super_duper_task --testis allowed (--testbeing at the wrong position) and doesn't throw an error.In this case the test DB is not created which isn't optimal if you want to test things out...
Steps to reproduce:
flexget execute --tasks super_duper_task --testsuper_duper_task--testright afterflexgetAdditional information: