watson
watson copied to clipboard
Some conditional statements never run because errors are always thrown when variables from commands aren't set to a value
For example, in task/install, the script will just fail without displaying any instructions the user to install the elementary-sdk package and if vscodium isn't found on the system, the script will also throw an error instead of continuing.
However, this seems to only occur when task/install is called from the watson script.
I've spotted these bugs by adding the -x flag to the scripts to aid with debugging.
A workaround for this is commenting out the set command used in the beginning of the scripts however, I wouldn't consider that as the solution.