Assertion class & maintanance.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3k
- Forks
- 101
- PR merge metrics
- No merged PRs in 30d
Description
hi, @lukeed ! is the project still maintained? I'd like to change [this class](https://github.com/lukeed/uvu/blob/9419247b8f93b61ce9a3aeca562f08491101a765/src/assert.js#L12) d.ts because all options there are optional partially, but in d.ts they must be all or nothing (or what am I missing?) :
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 src/assert.js at line 12 and locate the corresponding TypeScript declaration. Compare the runtime assertion options with the current d.ts optionality, then verify the intended all-or-nothing behavior with a focused type-check. Done means the declaration accurately represents the supported option combinations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100