`fatalError` prints the full path of the file, which leaks filesystem information from the machine that built the binary. Now that we release via CocoaPods, this is more critical.
The rule for unused optional binding was false triggering for pattern matching where the associated value was just an underscore. Additionally, pattern matching mixed with unused optional binding was not triggering in some cases.
New non triggering and triggering examples have been added for the failing cases, and new regular expressions are used to catch all the cases.
Modify the code in `File+SwiftLint` to expose full `NSTextCheckingResult` (and not just ranges) and rewire some pieces to use the new functions.
Fixes#1376
* master: (44 commits)
make valid_docs rule opt-in
update LineLengthConfiguration.consoleDescription after #1264
small refactoring after #1264
fix for_where violation in CompilerProtocolInitRule.swift
Add for_where rule
explicitly set podspec dependency versions
Add changelog entry
Fix existing violations
Navigate substructure even for different kinds
Small style changes
Modified so that kinds(forByteOffset:) does not require a separate filter() setup of the results
Changes from PR feedback. Long comments following code in a line will now trigger, configuration will now fail if invalud value types are set for options
Fix false positive on large_tuple when using generics inside a tuple
fix wording in changelog
disable docs rules in Swift 2.3 and later
Fix deadlock when stderr fills up OS buffer
small Danger/oss-check improvements
Fix links
Fix cleanup
Always use Xcode reporter on oss-check
...
* master: (41 commits)
Fix formatting in CHANGELOG.md
release 0.13.0
Update CHANGELOG.md
Fix check for trailing whitespace to return early
Fix checks for some inline comments
Replace check for comments to use SyntaxKind
Add configuration for trailing_whitespace to ignore comments
Unwanted space removed
- Lint issues fixed
Updated HTML Reporter
PR feedback
Add check on autocorrect for disabled range
Use `utf8.count` instead of `utf16.count` to byte range
Re-write `ExplicitInitRule` to `ASTRule`
added ExplicitInitRule
Updated CHANGELOG
HTML Reporter added
HTML Reporter added
Adds information about SwiftLint plugin for AppCode into README.md
added reasons why a new rule should be opt in
...
# Conflicts:
# Source/SwiftLintFramework/Extensions/File+SwiftLint.swift
# Source/SwiftLintFramework/Extensions/Structure+SwiftLint.swift
# Source/SwiftLintFramework/Rules/ColonRule.swift
# Source/SwiftLintFramework/Rules/CommaRule.swift
# Source/SwiftLintFramework/Rules/LegacyCGGeometryFunctionsRule.swift
# Source/SwiftLintFramework/Rules/LegacyConstantRule.swift
# Source/SwiftLintFramework/Rules/LegacyConstructorRule.swift
# Source/SwiftLintFramework/Rules/LegacyNSGeometryFunctionsRule.swift
# Source/SwiftLintFramework/Rules/LineLengthRule.swift
# Source/SwiftLintFramework/Rules/OperatorFunctionWhitespaceRule.swift
# Source/SwiftLintFramework/Rules/ReturnArrowWhitespaceRule.swift
# Source/SwiftLintFramework/Rules/RuleConfigurations/StatementPositionConfiguration.swift
# Source/SwiftLintFramework/Rules/StatementPositionRule.swift
# Source/SwiftLintFramework/Rules/TrailingWhitespaceRule.swift
# Tests/SwiftLintFramework/RuleConfigurationTests.swift
Marcelo Fabri
JP Simard
Marcelo Fabri
Daniel Rodríguez Troitiño
Keith Smiley
Michael Welles
rakaramos
Norio Nomura
J Cheyo Jimenez