BabyHint should not always rely on function.length to determine number of args
Open
BabyHint
- Dominant language
- JavaScript
- Stars
- 776
- Forks
- 180
- PR merge metrics
- No merged PRs in 30d
Description
It reports `new Array(1,2,3)` as an error, but shouldn't.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating BabyHint's argument-count checking logic and reproduce the reported new Array(1,2,3) case. Trace how function.length is used to decide the expected number of arguments, then verify that this call is no longer reported as an error while existing argument checks remain correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100