False positive for rule identifier_name in Xcode 10 beta

[Jeehut]

Hey guys,

I've just received a bug report in one of my open source projects here which is related to the identifier_name rule. Specifically here's the code where the rule triggers an error:

extension String {
    /// The type of allowed characters.
    ///
    /// - Numeric:          Allow all numbers from 0 to 9.
    /// - Alphabetic:       Allow all alphabetic characters ignoring case.
    /// - AlphaNumeric:     Allow both numbers and alphabetic characters ignoring case.
    /// - AllCharactersIn:  Allow all characters appearing within the specified String.
    public enum AllowedCharacters {
        case numeric
        case alphabetic
        case alphaNumeric
        case allCharactersIn(String) // Identifier Name Violation: Enum element name should only contain alphanumeric characters ...
    }
}

As you can see it's complaining about – probably – the braces which shouldn't be the case.

I'm using SwiftLint 0.25.1.

[Coder-256]

I fixed this in my PR #2232

[jorgecmoura]

I'm using Xcode 10 Beta 6 and I'm still getting this error. I'm using swiftlint 0.27.0.

Probably I'm missing some detail. Anyone else getting this error?

[shagedorn]

Maybe your command line tools are still set to an older version of Xcode?

Check via Xcode > Preferences > Locations, or the xcode-select -p command.

[jorgecmoura]

Good point. In fact they still were pointing to Xcode 9.4.1.

However, I'm still getting the error (command line tools now on 10.0).

[flashspys]

The problem was solved for me by upgrading to the latest swiftlint version and setting the xcode-select path to the beta xcode

[emadhegab]

still not working with latest official xcode release !

[jorgecmoura]

Sorry for the lack of update. Yes, is it working :)
It was probably something around having Xcode and Xcode-Beta running in same machine, together with some inability from me to quickly identify and fix that ;)

[emadhegab]

@jorgecmoura I don't have xcode beta any more and yet .. it's still give me same error!

[ValentinFesenko]

still not working with latest official xcode release !

I think you can manually choose the last version of the SwiftLint. It helped me.
Use this one:
pod 'SwiftLint', '~> 0.27'
instead of this
pod 'SwiftLint'

[geraldeersteling]

I'm on SwiftLint 0.27.0 and it still happens 😕, shouldn't this be fixed on that version?

[rafalszastok]

Small update. I noticed swiftlint is working properly, but danger extension use old 0.26 build.
PR: ashfurrow/danger-ruby-swiftlint#110

[kaybutter]

@rafalszastok You can work around this by telling danger to use the system swiftlint in your Dangerfile:

swiftlint.binary_path = "/usr/local/bin/swiftlint"

[dennishahn]

I still see this problem. We are using XCode 10, swift version 4.2 and swiftLint 0.27.0

[madhus1025]

I'm on SwiftLint 0.27.0 and it still happens 😕, shouldn't this be fixed on that version?

Any update on this ?