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

False positive in nimble_operator rule #2489

marcelofabri opened this Issue Nov 27, 2018 · 0 comments


None yet
1 participant
Copy link

marcelofabri commented Nov 27, 2018

New Issue Checklist

Describe the bug

Complete output when running SwiftLint, including the stack trace and command used
$ swiftlint --path file.swift --enable-all-rules --no-cache | grep nimble
Loading configuration from '.swiftlint.yml'
Linting Swift files at paths file.swift
Linting 'file.swift' (1/1)
Done linting! Found 2 violations, 0 serious in 1 file.
file.swift:2:2: warning: Nimble Operator Violation: Prefer Nimble operator overloads over free matcher functions. (nimble_operator)


  • SwiftLint version (run swiftlint version to be sure)? 0.28.2
  • Installation method used (Homebrew, CocoaPods, building from source, etc)? Homebrew
  • Paste your configuration file:
# insert yaml contents here


  • Which Xcode version are you using (check xcode-select -p)?


  • Do you have a sample that shows the issue? Run echo "[string here]" | swiftlint lint --no-cache --use-stdin --enable-all-rules
    to quickly test if your example is really demonstrating the issue. If your example is more
    complex, you can use swiftlint lint --path [file here] --no-cache --enable-all-rules.
// This triggers a violation:
foo.method {
    expect(value).to(equal(expectedValue), description: "Failed")
    return Bar(value: ())
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment