-
-
Notifications
You must be signed in to change notification settings - Fork 320
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
Add Swiftformat #375
Add Swiftformat #375
Conversation
Not sure I understand the reason for removing SwiftLint? SwiftFormat is great, and that's a good addition, but auto-formatting doesn't replaces the value of linting. It would just replace something like |
That's a good point. The Dangerfile has swiftformat set up to run as a linter, but I guess since it's not its primary goal, it doesn't provide the same level of linter that Swiftlint does. Let me check if I can configure both without conflicting with each other. |
Added Swiftlint back and fixed all the warnings and errors that we had in the project. Let mek now what you think @yonaskolb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
@@ -4,9 +4,6 @@ require 'fileutils' | |||
require 'colorize' | |||
|
|||
task :release_check do | |||
puts "Linting code".colorize(:cyan) | |||
system("swiftlint") || abort |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to keep this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's fine to get rid of it since we are running the linter on the PRs before they get merged.
Short description 📝
Add swiftformat and set up Danger to run it in a strict manner so that warnings are reported as errors.