Improve error messages
Open
@GanShun is already working on this.
Since May 9, 2019.
- Dominant language
- Go
- Stars
- 373
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
- Post a style guide for warnings and errors. How validation warnings are dealt with (I know we squelch some of these warnings). When to log.Print vs log.Fatal, ...
- Go through the code and fix up our error messages.
- Particularly, the "file too large" error needs to be improved. It's probably the most common error to run into. It prints a lot of information, but it would print some pointers on next steps.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.