[feature]: Making errors more descriptive
Open
@srinivaspendem is already working on this.
Since May 24, 2024.
✨feature
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Is there an existing issue for this?
- I have searched the existing issues
Summary
Example:
I entered a link to a public project, and tried to create a new issue, but wasn't allowed to. The error only said something very broad like 'something went wrong, try again'.
I had to talk to other team members to realize that I didn't click 'Join' in the Project, and that's all it took for me to be able to create a new issue.
Definitely several minutes there could have been saved with a more descriptive error.
Why should this be worked on?
It saves users' time and is more productive to have descriptive errors.
Instead of having to figure out what went wrong, if the error doesn't leave place to wonder, productivity is gained.
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.