All CollectingRules implement AnyCollectingRule, which is used to check
whether a linter will perform any collections and only print the
"Collecting" log message if so.
* Add LintableFilesVisitor
* Move LintCommand logic into LintOrAnalyzeCommand
to prepare for the upcoming analyze command
* Add AnalyzeCommand (not fully implemented yet in SwiftLintFramework)
* Add analyzerRules configuration member
* Add AnalyzerRule protocol
* Pass compiler arguments to validate/correct
* Add requiresFileOnDisk member to RuleDescription
This will be used by AnalyzerRules because they need a file on disk
to pass in the compiler arguments to SourceKit.
* Exclusively run AnalyzerRules when the Linter has compiler arguments
* Enable testing AnalyzerRules in TestHelpers
* Add ExplicitSelfRule
* Update documentation
* Fix `analyze --autocorrect`
* Improve performance of CompilerArgumentsExtractor
* Fix lint command actually running analyze
* Move File operations in TestHelpers into a private extension
* Add analyzer column to rules command and markdown documentation
* Use a Set literal
* Make AnalyzerRule inherit from OptInRule
* Mention analyzer_rules in readme
* Mention that analyzer rules are slow
The MIT license doesn't require that all files be prepended with this
licensing or copyright information. Realm confirmed that they're ok with this
change. This will enable some companies to contribute to SwiftLint and the
date & authorship information will remain accessible via git source control.
`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.
* 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
Paul Taykalo
Norio Nomura
Elliott Williams
JP Simard
Marcelo Fabri
Dani Vela
Yusuke Ohashi
John Szumski
Tom Quist
Marcelo Fabri
Michał Kałużny
Johnykutty Mathew
Matthew Ellis