ampproject / ampproject/amppackager
Improve error messages
Open
good first issue
- Dominant language
- Go
- Stars
- 141
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
Improve the error messages such that they are actionable by people who don't know code. Currently, they're pretty cryptic and mostly useful for devs.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating where errors are constructed and inventory the messages exposed to users; done means the relevant errors explain the problem and the next action in language non-developers can follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100