Allow configuration of rules to be either "warning" or "error"
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
As a developer,
When I write code that is not a best practice but not a build break,
I would like a "warning" message that is not an error.
Contributor guide
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
No files, tests, or entry points are named in the issue. Start by locating rule configuration and the code that reports rule violations, then determine how severity affects build failure. Done means a rule can be configured to emit either a warning or an error, with the warning not breaking the build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100