Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add nested type handling specification to file_name rule #2717

Closed
fredpi opened this issue Apr 12, 2019 · 0 comments

Comments

Projects
None yet
2 participants
@fredpi
Copy link
Contributor

commented Apr 12, 2019

Assuming I have a file that extends MyType.MySubtype like this:

extension MyType.MySubtype {
    // ...
}

I may call this file MyType.MySubtype+Extension.swift without triggering the file_name rule. I may also specify a custom file name suffix, so that I could name it MyType.MySubtypeExtension.swift.

In contrast, I cannot call my file MyTypeMySubtypeExtension.swift without triggering a warning. As such a naming (without a second . character in the file naming) may be preferred by some, I propose to extend the file_name configurability to allow for custom nested type separators (with . remaining the default).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.