Discussion: numeric error codes
- Dominant language
- Go
- Stars
- 44
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
I found this code.
https://github.com/bosnet/sebak/blob/b01b08b1e8e4aae6a1d86ba5b64eccb3d1ae2277/lib/error/errors.go#L4-L11
Honestly, I'm skeptic for numeric error code. So, I want to discuss about that.
Why I dislike numeric error code is It is not meaningful. We don't know what error code is mean when we see the code. So, we look for what the code mean in above file.
Contributor guide
Research direction
Start with lib/error/errors.go at lines 4-11 and inspect how the numeric error codes are used elsewhere in the repository. The issue is a discussion rather than a defined task, so completion requires an agreed direction for replacing or retaining the codes and a clearly scoped follow-up change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100