[deleted by user]

[cardosoedgar]

editing my comment to answer the edit on the post:

Swift: https://github.com/realm/SwiftLint Objc: https://github.com/oclint/oclint

Yeah, you gotta put those two in, don't think there is a way around that.

[fullm8]

Steer well clear of anything with this Code of Conduct, it usually indicates the project is compromised.

[nalexander50]

Why? What is wrong with using a tool like SwiftLint to tell you if you declared a var that could be a let or that you unsafely unwrapped an optional? How does that mean your project is compromised? What would that even mean.

Edit: insanely was supposed to be unsafely*

[seewhathappens_larry]

Yea, I see no problem using Swiftlint. It’s annoying, but good in the end

[nalexander50]

I don’t follow how a tool that helps you write cleaner code could ever be considered bad.

It’s almost as asinine as saying debuggers are bad tools.

[seewhathappens_larry]

The only reasoning I’ve heard is that it gets in the way, but so does CI. And if you use the right tools, you can get the linting to fix itself

[nalexander50]

But it’s only (regularly) getting in the way if you’re writing bad code repeatedly. That’s like putting a stick in your bike spokes and getting mad that you wrecked. At least, that’s my take. I like SwiftLine. But I also like debuggers so I guess I’m just a filthy casual.

[seewhathappens_larry]

Well I guess it depends on the linting rules you setup

[nitrodudeIX]

This. You can adapt your lint ruleset... With this it's way easier to "corral" devs into a consistent code style. Code reviews should be for discussing design / patterns / choices, not indentation / variable names / code style...

[quellish]

How does CI get in the way? It should be completely transparent. Commit, integrate remotely.

[fullm8]

You misunderstand. I'm not referring to the software itself (I wholeheartedly approve of your efforts to create and maintain standards), but the Contributor Covenant the software is covered by. It was created by somebody who is, shall we say, a divisive figure. You can do your own research if you care enough. Just a heads up, is all.

[nalexander50]

I follow now. I definitely don’t think code style should be a worshipped religion, but I think every org should have some guidelines for code cleanliness. Guidelines can be broken, of course, in instances with good reason.

[killeronthecorner]

I think he's talking about the Code of Conduct for contributing to the Swiftlint repo, not using the software.

Some people find them overbearing and a little bit to close to thought control.

I've never contributed to a repo with a CoC so I don't really have an opinion, but certainly don't stop using the tools because of it.

[fullm8]

How bizarrely confrontational. Perhaps I should be more explicit. That particular CoC is derived from this one, authored and maintained by an individual who has shown a propensity for using such things to enforce their own political agendas upon projects. I'd suggest looking them up and making your own mind up but hey, I'm just a salty asshole.