Have an option to cap lints on dependencies to "warn" instead of "allow"
Open
Nobody has claimed this yet.
A-configuration
A-crate-dependencies
A-diagnostics
A-lints
C-feature-request
Command-build
S-needs-design
- Dominant language
- Rust
- Stars
- 15.5k
- Forks
- 3k
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 51
Description
Never showing any warnings for upstream deps can hide issues from the user (be it a bug in the library or a future-compatibility lint). Showing them will make those issues more visible and might cause them to get fixed earlier.
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
The issue names no files, tests, or entry points. Start by locating Cargo's handling of lints for dependencies and the existing configuration or command-line options; done means users can choose to cap dependency lints at "warn" instead of "allow" and see the resulting warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100