Currently config is loaded (via yargs) before everything because it's required for core behaviour like logging. However, adapters and scripts might also make use of yargs interfaces command line help text etc, so it would be nice if they could define additional options after the adapter is chosen through the initial config loading.
No idea how this would work, because using the --help would probably exit before adapters are loaded. Might need to refactor a fair amount of load ordering.
Currently config is loaded (via yargs) before everything because it's required for core behaviour like logging. However, adapters and scripts might also make use of yargs interfaces command line help text etc, so it would be nice if they could define additional options after the adapter is chosen through the initial config loading.
No idea how this would work, because using the --help would probably exit before adapters are loaded. Might need to refactor a fair amount of load ordering.