Add opt-in force unwrapping rule #421
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The rule will create a warning for all force unwrappings
- Changed the `Location` of the StyleViolation to point to the `!` that actually does the unwrapping
|
I think this would only really make sense in certain parts of a project, if ever, which is why it's an opt-in rule. |
|
This is an opt-in rule, and probably fine as-is. There's just the one false positive in the SwiftLint codebase mentioned in #374 (comment). |
jpsim
added a commit
that referenced
this pull request
Jan 26, 2016
Add opt-in force unwrapping rule
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Continued from #374 /cc @scottrhoyt @norio-nomura @Argent