-
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
TODO & FIXME #150
Comments
If you'd like to disable this for your project you can add this to your disabled_rules:
- todo |
Also the readme says:
So I don't think it's a huge deal as more rules are added to SwiftLint. Especially since they can be easily disabled. |
I know how to disable it, thank you though. |
I added that in because IMO the role of a linter is to show you the parts of your code that need your attention and ultimately need to be fixed. TODOs and FIXMEs are one way to do this. |
@jpsim I'm not sure I understand. Are you saying the reason for the warning is to actually show and bring the todo to your attention so that you may implement the actual todo? I ask because the warning given by swift-lint seems to be to not use TODO's. |
Yes. |
@jpsim The message given by Swift lint does not imply that though: SwiftLint displays: "Todo Violation: TODOs should be avoided...." |
If you have an improvement in mind, feel free to file a PR. |
@jpsill Will do! |
I also first thought that it discourages using TODOs but it actually encourages them by supporting them and making them more useful through this rule :D Maybe the message should be changed to "consider doing / fixing what the TODO suggests", though ^^ |
Pull Request #2069 has been added to fix this issue. |
The author's intent in adding If you want to suppress this warning, you can turn off this rule, which is on by default, in |
Why does the linter checks for TODO/FIXME statements? I thought you guys are using GitHub's Swift Style Guide as a guideline which has all rules explained.
If you add rules of your own, please document the reasoning behind it.
The text was updated successfully, but these errors were encountered: