Is your feature request related to a problem? Please describe.
The current code builds any and all commands from the main configs.json file, only to execute them regardless of whether or not the command even succeeds or not. To circumvent this problem, a first step of lessening the calculations required, a config could be skipped based on if the Command.Name exists within the %PATH%.
Describe the solution you'd like
Over-all, general error handling and logging should be added to the project, and to start off with some general performance improvements and error handling, there could be an easy check for whether or not any given program inside a command even exists in the first place.
Is your feature request related to a problem? Please describe. The current code builds any and all commands from the main
configs.json
file, only to execute them regardless of whether or not the command even succeeds or not. To circumvent this problem, a first step of lessening the calculations required, a config could be skipped based on if theCommand.Name
exists within the%PATH%
.Describe the solution you'd like Over-all, general error handling and logging should be added to the project, and to start off with some general performance improvements and error handling, there could be an easy check for whether or not any given program inside a command even exists in the first place.