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.

Sign up for GitHub

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

Jump to bottom

empty_count sometimes throws warning even when the isEmpty property doesn't exist #2083

Closed
2 tasks done
heidiproske opened this issue Mar 3, 2018 · 1 comment
Closed
2 tasks done

empty_count sometimes throws warning even when the isEmpty property doesn't exist #2083

heidiproske opened this issue Mar 3, 2018 · 1 comment

Comments

@heidiproske
Copy link

heidiproske commented Mar 3, 2018 •
edited
Loading

New Issue Checklist

Bug Report

As you can see, I'm getting the empty_count warning thrown in my UITests target below. The .isEmpty property doesn't actually exist on XCUIElementQuery. I've seen this happen in other scenarios too on properties that don't support it. Does everyone just add an explicit swiftlint:disable:next empty_count everywhere the warning is thrown where it can't be fixed?

screen shot 2018-03-02 at 7 20 23 pm

Environment

  • SwiftLint version (run swiftlint version to be sure)? 0.25.0
  • Installation method used (Homebrew, CocoaPods, building from source, etc)? cocoapods
@heidiproske
Copy link
Author

Just saw comment of #827 where it's recommended to just code around it (since there are these false positives) :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@heidiproske