Don't enforce inside returns with non-nil errors #52
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.
If a function has a struct return type alongside an error,
it's pretty standard to do this:
There's no reason to enforce required fields on the struct
because the contract is that the struct value is to be ignored
if the error is non-nil.
This change adds support to detect these cases and ignore them.
It is a bit messier than "ignore if part of return with non-nil error"
because we still want to enforce required fields if the non-nil error
itself is the thing with required fields, e.g.
Resolves #37