This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
[Lint] Fixes some trivial SwiftLint warnings #516
Closed
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.
Description
This is the first follow-up smaller PR to #104. Together with the other PRs I will be posting, all SwiftLint warnings should be fixed to allow us to enable the
--strict
mode of SwiftLint on the CI to prevent any new warnings getting merged in the future.Related PRs
#518, #522, #527, #531, #534.
Note that all these PRs are completely independent and can be merged in any order.