Configurable stack traces #15
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The stack traces are very useful, but as a customer facing CLI, it can be rather verbose and is useless unless they know the source code.
This introduces the concept of a debug mode for configuring when to print out the stack trace. Now the command will only print out stack traces when run with
GRUNTWORK_DEBUG=1
.Note: I couldn't find a good way to unit test this, given that
checkForErrorsAndExit
kills the process. For now, here is the manual test demo:Without env:
With env: