Closed pixyzehn closed 7 years ago
We can also use SwiftFormat. The benefit of having SwiftFormat
over SwiftLint
is, it automate the process of maintaining one syntax styling. Whereas in SwiftLint
it will generate all the warning and developer have to resolve these.
I would like a solution where a tool does this work for me, automatically.
@aksswami I don't know the details, but you may use the same things by using swiftlint autocorrect
.
@JohnSundell Could you check my update?
We could just execute swiftlint
in our Travis & BuddyBuild scripts, right?
@JohnSundell No problem:) Yes, we want!
We could just execute
swiftlint
in our Travis & BuddyBuild scripts, right?
That's right! But I think it's better to set it in other PR for now if possible. It needs some adjustments like installing SwiftLint by homebrew in Travis...
@pixyzehn Sounds great! π Do you wanna create an issue for tracking adding this to CI? π
@JohnSundell Yes, I want! I'll investigate itπ Thanks again!
Introduced SwiftLint and Fixed warnings and errors. Now
Marathon
doesn't have xcodeproj, so we just run SwiftLint in CI or each local env.In
type_body_length
andfile_length
, I adjusted the boundary value based on the following warnings and errorsRef: https://github.com/krzysztofzablocki/Sourcery/blob/master/.swiftlint.yml https://www.buddybuild.com/blog/customizing-the-build-process