scratchfoundation / scratchfoundation/scratch-parser
Always return an error object
Open
Nobody has claimed this yet.
ergonomics
- Dominant language
- JavaScript
- Stars
- 71
- Forks
- 81
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
Right now errors returned through the callback interface from scratch-parser can be of three types: objects, strings, or Errors. As we have done in other repos it would be good to normalize this to always return an error object.
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 tracing the callback error paths in scratch-parser and identify where object, string, and Error values are returned. Check how existing tests exercise callback errors. Done means every callback error path consistently returns an error object, with coverage for the previously supported error forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100