rescript-lang / rescript-lang/experimental-rescript-webapi
How to model Errors
Open
Nobody has claimed this yet.
- Dominant language
- ReScript
- Stars
- 40
- Forks
- 11
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 12
Description
Hi again,
How do we want to model https://developer.mozilla.org/en-US/docs/Web/API/DOMException?
Just as an interface or do we want to tied this to Error.t somehow?
Contributor guide
No contributing guide indexed for this repository
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 the linked MDN DOMException reference and review how the project currently models Error.t. Resolve whether DOMException should be represented as an interface or connected to Error.t; the issue is complete when that modeling choice is agreed and applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100