notes:
Tested against the 017-GIT version (unmodified), successful output was identical, as were the tested (non-fatal) error states. However the output for many fatal errors is different, previously you would see python errors or cat errors, however now the majority of them should be handled by/show output from the Die function.
With the new Die based error messages, it may be helpful to eventually add a --no-color option in the future. I have no plans of implementing it at the moment, just wanted to take note of it.
in testing, non-fatal error also showed identical responses when fed malformed data. An example being:
1:'@%VAR1%@' 2:'@%VAR2%@' 3:'@%VAR3%@' # good outputs 1:'value1' 2:'value2' 3:'value3'
1:'@%VAR1' 2:'@%VAR2%@' 3:'@%VAR3%@' # bad outputs 1:'' 3:'value3'
1:'%@VAR1@%' # bad hangs perpetually
I'm unsure what line of code is causing the 3rd example to hang, nor do I have plans of fixing it at the moment; I am simply making note of its existance.
For Compile Issue #47
Python3
logic into it's own file/bin/ApplyVariablesCore
cat
Die
to handle the error messageApplyVariables: <FILENAME>: failed
notes: Tested against the
017-GIT
version (unmodified), successful output was identical, as were the tested (non-fatal) error states. However the output for many fatal errors is different, previously you would seepython
errors orcat
errors, however now the majority of them should be handled by/show output from theDie
function.With the new
Die
based error messages, it may be helpful to eventually add a--no-color
option in the future. I have no plans of implementing it at the moment, just wanted to take note of it.in testing, non-fatal error also showed identical responses when fed malformed data. An example being:
I'm unsure what line of code is causing the 3rd example to hang, nor do I have plans of fixing it at the moment; I am simply making note of its existance.