m-a-r-c-e-l-i-n-o / unistack / 65

Builds Branch Commit Type Ran Committer Via Coverage
65 master refactor: Standardize communication across the system Previously, the communication object was loosely established, leaving plenty of room for ad hoc messaging. This commit introduces and interface for sending objects. push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
64 master feat: Validate empty user command Previously, an empty command would have propagated through the system and returned as not found. This commit makes that feedback immidiate and gives the user a change to re-submit a non-empty command. push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
63 master feat: Prompt user for commands Previously, the user had no control of what happened in their environment and that's no good. This commit introduces a question prompt that the user can submit commands to. push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
62 master refactor: Implement exit strategy for core process in CLI Previously, there was no strategy, and the errors would output directly to the terminal. This commit implements an exit strategy based on four exit codes and a catch all for exits outside ... push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
61 master refactor: Making things make a little more sense, again. This time not out of absolute necessity, but for the sake of optimum code readability. Changes include: -Rearrangement of core, cli, and bin methods and variables -Changing core promise ch... push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
60 master refactor: Making things make a little more sense, again. This time not out of absolute necessity, but for the sake of optimum code readability. Changes include: -Rearrangement of core, cli, and bin methods and variables -Changing core promise ch... push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
59 master refactor: Making things make a little more sense, again. This time not out of absolute necessity, but for the sake of optimum code readability. Changes include: -Rearrangement of core methods and variables -Changing core promise chains to async/... push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
58 master refactor: Making things make a little more sense, again. This time not out of absolute necessity, but for the sake of optimum code readability. Changes include: -Rearrangement of core methods and variables -Changing core promise chains to async/... push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
57 master refactor: Add error handling to the CLI Previously, the CLI was at a loss. This commit makes the CLI a winner. push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
55 master refactor: Add error handling to the CLI Previously, the CLI was at a loss. This commit makes the CLI a winner. push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
54 master refactor: Check if directory is a unistack env before starting it Previously, unistack would try to start its dev environment without knowing whether or not that directory contains the necessary fiels. This commit fixes that by creating a method ... push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
53 master refactor: Check if directory is a unistack env before starting it Previously, unistack would try to start its dev environment without knowing whether or not that directory contains the necessary fiels. This commit fixes that by creating a method ... push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
52 master refactor: Ensure errors are emitted to CLI Previously, errors were handled at the process level. This commit ensures that errors are encapsulated by promises and emitted to the CLI for further analysis. push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
51 master test: Ensure correct test description for starting dev environment Refers to the "startDevEnvironment" method. push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done
50 master refactor: Make empty environment validation method less ambiguous Previously, the method to check if the environment is empty was called "validateEnvironmentRoot". This commit changes that to "isEnvironmentEmpty" in preparation for another method... push m-a-r-c-e-l-i-n-o travis-ci pending completion   set done