When running tests with the latest nanorc code on the production/v4 branch, I noticed complaints about failures in running the "lower" function on an empty object. I traced this to a lack of a default value in the --run-type option that I added to nanorc in cli.py recently. The code change in this PR fixes this bug.
Before the change, we can not start runs with nanorc without explicitly specifying the --run-type start/start_run parameter.
With this change, a default value of "TEST" is assigned to the run_type and subsequent operations such as "lower" now work.
When running tests with the latest
nanorccode on theproduction/v4branch, I noticed complaints about failures in running the "lower" function on an empty object. I traced this to a lack of a default value in the --run-type option that I added tonanorcin cli.py recently. The code change in this PR fixes this bug.Before the change, we can not start runs with
nanorcwithout explicitly specifying the --run-type start/start_run parameter.With this change, a default value of "TEST" is assigned to the run_type and subsequent operations such as "lower" now work.