Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Request: add --lenient lint parameter to only generate warnings #1322

Closed
NachoSoto opened this issue Feb 20, 2017 · 3 comments
Closed

Request: add --lenient lint parameter to only generate warnings #1322

NachoSoto opened this issue Feb 20, 2017 · 3 comments
Labels
enhancement Ideas for improvements of existing features and rules.

Comments

@NachoSoto
Copy link
Contributor

Just like --strict, it would be nice to be able to only generate warnings.

A use case for me is that I want to run the linter for all files when I run all the tests, but I don't want it to fail, because I want to distinguish a linting (ran separately) problem versus failed tests.
@marcelofabri marcelofabri added the enhancement Ideas for improvements of existing features and rules. label Feb 21, 2017
@jpsim
Copy link
Collaborator

jpsim commented Mar 10, 2017

I see how that could be useful. Until we add such an option, you could hack it yourself:

swiftlint | sed s/error:/warning:/g

This was referenced Mar 15, 2017
Closed
Merged
@jpsim
Copy link
Collaborator

jpsim commented Mar 23, 2017

added in #1364.

@jpsim jpsim closed this as completed Mar 23, 2017
@NachoSoto
Copy link
Contributor Author

Awesome! 🎉

mattrubin added a commit to mattrubin/SwiftGit2 that referenced this issue Apr 24, 2017
@mattrubin
Run the SwiftLint build phase with the --lenient flag
f10c8d0 
Running SwiftLint in "lenient" mode will only generate warnings, preventing the linter from causing the build to fail.
realm/SwiftLint#1322
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Ideas for improvements of existing features and rules.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jpsim @NachoSoto @marcelofabri