Ensure that errors thrown inside snaps are presented in a readable format to developers
Open
Nobody has claimed this yet.
area-developing
snaps-unrefined-backlog
- Dominant language
- TypeScript
- Stars
- 853
- Forks
- 662
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 8
Description
Errors thrown or logged inside snaps should be presented in a readable format in order to be useful for debugging purposes. Currently, it is nearly impossible to decipher where an error is actually coming from.
**AC**
Errors appear in the console in a readable format, which makes it easy for the developer to understand where the error is coming from.
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.
Research direction
Start by reproducing an error thrown or logged inside a snap and inspect how it currently appears in the console. The work is done when both error types are presented in a readable format that lets developers understand where each error originates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100