-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New MARK rule does not detect "//MARK: - sometext" #805
Comments
Hello. Why you think that the construction should be marked as warning? |
No space after // |
.. I can't to find any apple's guidelines, in which says, that need space between "//" and "MARK:" (( Have you some links to share? |
take a look at new MARK rule, please. #749 |
That's right. This issue has been resolved. And in repository it is already exists. Please, try to update your SwiftLint on your device For example, on my computer, it would be something like this command: "brew update && brew upgrade |
Ok, I'll be more specific: ~ $ swiftlint version
0.12.0
~ $ echo //MARK: mark text | swiftlint lint --use-stdin
<nopath>:1:2: warning: Mark Violation: MARK comment should be in valid format. (mark)
Done linting! Found 1 violation, 0 serious in 1 file.
$ echo // MARK: mark text | swiftlint lint --use-stdin
Done linting! Found 0 violations, 0 serious in 1 file.
$ echo //MARK: - mark text | swiftlint lint --use-stdin
Done linting! Found 0 violations, 0 serious in 1 file. The last line should produce a warning |
Thank you for your patience in explaining the issue's reasons. The latest version of SwiftLint, which is currently has stored in the repository, provided by your version of the code is described approximately by such rule: "
This variants of behavior is specifically described and located in the the exclusion. |
Sorry it took a while to get to this. I've pushed a fix in #888. |
Latest swiftlint doesn't detect
//MARK: - mark text
as a warning, but it should. Am i right?The text was updated successfully, but these errors were encountered: