arethetypeswrong / arethetypeswrong/arethetypeswrong.github.io
Indicate when JS is unanalyzable
Open
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Description
attw doesn’t show any problems if it can’t detect them, even if that’s only because the JS couldn’t be analyzed for some reason. It would be nice to indicate if a check passed only because we couldn’t analyze the JS.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name a file, test, or entry point. Start by locating the code that analyzes JavaScript and reports check results, then determine how an unanalyzable case is represented. Done means a check is visibly distinguished when it passes only because the JavaScript could not be analyzed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100