Skip to content

Add -s option to codesniffer-run for "strict" mode.#72

Merged
beporter merged 1 commit into
masterfrom
f/codesniffer-strict-mode
Feb 2, 2016
Merged

Add -s option to codesniffer-run for "strict" mode.#72
beporter merged 1 commit into
masterfrom
f/codesniffer-strict-mode

Conversation

@beporter

@beporter beporter commented Feb 2, 2016

Copy link
Copy Markdown
Contributor

The intent behind this change is to combat a general desensitization to sniff warnings. Issues are slipping past developers because they end up getting buried in a bunch of TODO warnings. We want to increase the signal to noise ratio while still making it straightforward to review the TODO markers via the code sniffer. loadsys/loadsys_codesniffer#50 reduces the default severity for TODO warnings to suppress them during normal runs. (The -n switch will continue to suppress all warnings.) The addition of the -s ("strict") switch in this PR will reduce the warning threshold to make TODO marker warnings appear in the output.

The -s flag can be used locally to review TODOs or in Travis builds to enforce their complete absence.

Also enables color output by default.

Reduces the warning threshold to make TODO marker warnings appear (now disabled by default in the Loadsys Coding Standard.)

The -s flag can be used locally to review TODOs or in Travis builds to enforce their complete absence.

Also enables color output by default.
@justinyost

Copy link
Copy Markdown
Contributor

Do we want the default to be strict, and then explicitly change it for Travis?

@beporter

beporter commented Feb 2, 2016

Copy link
Copy Markdown
Contributor Author

I'm thinking from the perspective of "the most typed case," which I believe is a developer running it locally. The .travis.yml file only has be changed once to invoke strict (or the converse "relaxed" mode), and it will run that way "all the time" from then on, but devs would need to know and remember to include the switch almost all the time in the case of defaulting to strict and needing to silence the noise. I want that to be the easiest to access case.

@justinyost

Copy link
Copy Markdown
Contributor

Ok, fair enough.

@justinyost

Copy link
Copy Markdown
Contributor

👍

beporter added a commit that referenced this pull request Feb 2, 2016
Add -s option to codesniffer-run for "strict" mode.
@beporter beporter merged commit 4579a66 into master Feb 2, 2016
@beporter beporter deleted the f/codesniffer-strict-mode branch February 2, 2016 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants