Return error instead of using log.Fatal #380
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.
I took a detour when working on #379, because this has become a pretty major issue and I just want to get it fixed once and for all.
Turns out using
log.Fatal
from template functions was a terrible idea. Makes it much harder to properly handle/display/track errors, andtext/template
handles them decently anyway.The basic goal here is to remove all uses of
log.Fatal
orlog.Fatalf
, and instead change function signatures to return errors instead.Signed-off-by: Dave Henderson [email protected]