`unused-parameter` rule should not trigger on parameters used for their type
Open
Nobody has claimed this yet.
discussion
- Dominant language
- Swift
- Stars
- 19.7k
- Forks
- 2.3k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- I've Updated SwiftLint to the latest version.
- I've searched for existing GitHub issues.
Bug Description
It should not report for cases where the parameter is used for its type and not value.
extension Data {
func jsonDecoded<T: Decodable>(ofType type: T.Type) throws -> T {
try JSONDecoder().decode(T.self, from: self)
}
}
Here the type parameter decides the return type.
Environment
- SwiftLint version: 0.56.0
- Xcode version: Xcode 15.4, Build version 15F31d
- Installation method used: Installer
- Configuration file:
only_rules:
- unused_parameter
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
Start with the unused_parameter rule and reproduce the report using the Swift example and the provided only_rules configuration. Check whether the rule treats the parameter’s use for its type as a use; done means this example no longer triggers the rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100