Error Handling
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
The scripting API makes use of errors being available in ECMAScript (e.g., TypeError).
Moreover, also other errors such as NotSupportedError or NotFoundError are used which are not available in ECMAScript. Instead those errors are defined here.
We need to have a good set of errors that work for JavaScript/Typescript and browser environments.
For example, NotSupportedError and NotFoundError need to be defined in TypeScript definitions before they can be used in TS.
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 with typescript/index.d.ts and review the ECMAScript errors named in the issue alongside the DOMException error names linked from WebIDL. Inventory the errors used by the scripting API and determine the intended JavaScript, TypeScript, and browser-compatible set; done means the supported errors are consistently defined and usable in those environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100