Lint for console.log
Open
lint
- Dominant language
- TypeScript
- Stars
- 131
- Forks
- 67
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 10
Description
We've had a few cases of an errant console.log checked in to production. We should lint for these.
Contributor guide
Research direction
Start by locating the repository's lint configuration and the TypeScript source that can emit console.log calls. Define the lint behavior for these calls and verify that the lint run reports production occurrences without blocking intended usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100