refectorying: Used fmt.Errorf() instead of errors.New() #205

yj-yoo · 2024-04-15T00:15:42Z

In the next article, we recommend fmt.Errorf() when errors require formatting and use errors.New() for static error messages. (https://www.digitalocean.com/community/tutorials/how-to-add-extra-information-to-errors-in-go)

What type of PR is this?
/kind cleanup

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

none

- In the next article, we recommend fmt.Errorf() when errors require formatting and use errors.New() for static error messages. (https://www.digitalocean.com/community/tutorials/how-to-add-extra-information-to-errors-in-go) Signed-off-by: Youngjun <yj.yoo@okestro.com>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

refectorying: Used fmt.Errorf() instead of errors.New() #205

refectorying: Used fmt.Errorf() instead of errors.New() #205

yj-yoo commented Apr 15, 2024

refectorying: Used fmt.Errorf() instead of errors.New() #205

Are you sure you want to change the base?

refectorying: Used fmt.Errorf() instead of errors.New() #205

Conversation

yj-yoo commented Apr 15, 2024