-
Notifications
You must be signed in to change notification settings - Fork 23
Open
Labels
good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Description
make sure that some context is being added at every notable function to make debugging easier.
currently, there are several locations in the code where we wrap an error return without adding any meaningful context. this can make debugging challenging as it is not clear where an error originated from when multiple call paths could return a similar error message.
this issue is about adding more context to errors that are returned. the idea being that when we see code like:
if err != nil {
return nil, err
}we should transform into something that adds context, like this:
if err != nil {
return nil, fmt.Errorf("return error from function X because Y thing didn't happen, error: %w", err)
}patrostkowski and moko-poi
Metadata
Metadata
Assignees
Labels
good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.Categorizes issue or PR as related to cleaning up code, process, or technical debt.