Improve ErrorWithExitCode #30
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm blocked on this in my other PR so going to go ahead and merge+release this, but feedback is still welcome. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I noticed that the user experience for returning
ErrorWithExitCodeisn't quite great, so I made a few improvements here:WithStackTraceandErrorWithExitCode, so that you can get both a stack trace and exit with exit code.ErrorWithExitCode{ Err = Deployment failed, ExitCode = 1 }checkForErrorsAndExitso we can test the exit code functionality without the test exiting due to the call toos.Exit.