Decide on the convention for error messages
Open
enhancement
error reporting
- Dominant language
- Go
- Stars
- 1.8k
- Forks
- 263
- PR merge metrics
- No merged PRs in 30d
Description
For example:
`RUNTIME ERROR: couldn't open import "no chance a file with this name exists": no match locally or in the Jsonnet library paths`
vs
`RUNTIME ERROR: Couldn't open import "no chance a file with this name exists": no match locally or in the Jsonnet library paths.`
We need to decide how we want it and keep it consistent. It may require changing APIs slightly, so that errors from Go (file not found, etc.) won't break our convention and that golint is happy.
Contributor guide
Assessment
This issue has not been assessed yet.