search

fastred / IBAnalyzer

Find common xib and storyboard-related problems without running your app or writing unit tests.
http://holko.pl
MIT License
951 stars 26 forks source link

SwiftLint integration #7

Closed wokalski closed 7 years ago

wokalski commented 7 years ago

I don't use neither IBAnalyzer nor SwiftLint but I guess it would be marvellous to be able to lint for something like this. It might not make sense though so feel free to close.

ldrr commented 7 years ago

+1

ldiqual commented 7 years ago

While it seems neat, I'm not sure it is the role of a swift linter to lint iOS/OSX related assets. SwiftLint is purely for making sure that your swift code is properly styled while covering stuff like "don't use optional force unwrapping", but IBs are part of a bigger environment that swift is barely related with. Swift also runs on linux, android, and there's a big push for backend server in swift, all of those unrelated to IBs.

fastred commented 7 years ago

I tend to agree with @ldiqual here. One more reason is that SwiftLint operates on a file-by-file basis whereas IBAnalyzer requires knowledge about all Swift types in the project (at least for the currently implemented warnings).

IBAnalyzer is in a super-early phase of life. Ideally I'd like it to be distributed through CocoaPods or Homebrew and emit warnings visible in the Issue navigator, similarly to SwiftLint.

I'm going to close this issue for now. Feel free to reopen.

wokalski commented 7 years ago

sure, I was aware that it might not make sense. what bothers me though - is there no tool to rule them all when it comes to linting iOS projects?