Fixed multiple SwiftLint violations #772
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I ran SwiftLint against Periphery (and vice versa), and there were many rules with a small number of violations and trivial fixes.
A lot of changes were just whitespace (trailing spaces, more than one new line at the end of a file) - some small code changes to equivalent constructs.
Of the remaining violations, quite a few are in test fixtures and intentional. I didn't want to start sprinkling
// swiftlint:disable:next
statements, but that would be the obvious thing to do with these.Before:
After: