ndejong / env-alias Goto Github PK

Exceptions raised by env-alias-generator echo to stdout that are then passed to alias which then cause confusion

For example, if the user has a poorly formatted source-file that is missing a value to be created in the env-alias-generator stage, then this will raise an exception like below

env-alias v0.4.0
ERROR: Unable to find data at supplied path in YAML content.
'command_modules'

Because this is sent to stdout it is then passed through to the alias stage

alias env-awesomething='source <(env-alias-generator /home/ndejong/envs/awesomething.yml)'

This then provides the user with a difficult to understand situation

ndejong@computer ~/project$ env-awesomething
Usage: env-alias <alias> [-d] <config.yml>
ERROR:: command not found
command_modules: command not found

At minimum, the exception ought to write to stderr so the user can better understand the situation and track down their problem faster