tc39 / tc39/proposal-error-code-property
Conflict with DOMException
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 38
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
I don't like this as DOMException has Error in its prototype chain so we'd end up shadowing this new property making it useless in a lot of web platform code.
The web platform has established a pattern whereby if the name field is not granular enough you create a subclass of DOMException for the domain in question with specific fields that make sense.
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
No files, tests, or entry points are named. Start by reading the proposal discussion and checking how DOMException inherits from Error; determine whether the proposed property would be shadowed in web platform code. Done requires a resolved design direction for handling granular error information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100