This would address the outstanding issue of how we do parameter validation.
Currently, we can only validate the user's parameters file when we know what workflow they're going to run. This gets tricky because of two conflicting scenarios:
Scenario 1: The user only wants to run one step, and they don't need to specify options for 15 other steps; the user wants the program to fill in default values silently.
Scenario 2: The user mistakenly specified the parameters in the wrong place; the user wants the program to fill in default values but notify the user.
Also relates to #12 (the task of adding a validate verb to validate configuration/parameter input files).
This would address the outstanding issue of how we do parameter validation.
Currently, we can only validate the user's parameters file when we know what workflow they're going to run. This gets tricky because of two conflicting scenarios:
Also relates to #12 (the task of adding a
validate
verb to validate configuration/parameter input files).