`file_name` should be configurable to (or maybe always) exclude files whose types & extensions are all `private` and/or `fileprivate`
Open
Nobody has claimed this yet.
enhancement
- 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.
Feature or Enhancement Proposal
file_name should be configurable to (or maybe always) exclude files whose types & extensions are all private and/or fileprivate (such files would only be useful if they contain a global function that uses the private and/or fileprivate types).
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 by locating the file_name rule implementation and its tests. Determine how configuration should control files containing only private and/or fileprivate types and extensions, including the stated global-function exception, then add coverage that makes the chosen behavior explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100