"no_empty_block" causes default functions in protocols to be detected
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
- Updated SwiftLint to the latest version
0.56.1 - I searched for existing GitHub issues
- yes
The rule "no_empty_block" causes default functions in protocols to be detected. It should specifically exclude functions in protocols from this detection.
for example
protocol Animal {
func run()
}
extension Animal {
func run() {}
}
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 no_empty_block rule and reproduce the protocol-extension example from the issue. Verify that default functions in protocol extensions are excluded while other empty blocks remain detected, then run the relevant SwiftLint tests to confirm the behavior.
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
- Clearly specified
- Newbie friendliness
- 35/100