`file_name` should be configurable to (or maybe always) exclude files whose types & extensions are all `private` and/or `fileprivate`

[rgoldberg]

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).

[kapitoshka438]

Why?

[rgoldberg]

@kapitoshka438 Such private & fileprivate types & extensions are just helpers, not part of the public API of the file, so shouldn't be in the file name (e.g., a helper private extension String for a global function in a file shouldn't require me to explicitly exclude the file to avoid a file_name violation).

[kapitoshka438]

@rgoldberg how would you name a file containing a private String extension which is, let's say, a helper for some formatting features?

[rgoldberg]

@kapitoshka438 Obviously after the global function(s) in the file.