refactor error handling #48
Merged
Conversation
This file contains 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 think this is good, thanks. I'm happy with the naming at least, and we can change the name in a follow up if folks have string feelings. |
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.
In its current form - a lot of the
testcode treats messages (warnandfail) produced by theregocheck process as "first class" go errors. This results in some confusion and tangling of dependancies when having to guard against and handle other types of errors, which could come from failing to open a file or downstream errors thrown by the rego compiler itself.This patch proposes refactoring the return type of many internal methods to be of
(checkResult, error)to make this behavior more explicit. I'm very open to different names or another approach if other maintainers think that would be best!