Skip to content
This repository has been archived by the owner on Mar 23, 2024. It is now read-only.

CLI: Incorrect ERRORLEVEL being reported to stdOut #212

Closed
am11 opened this issue Jan 24, 2014 · 3 comments · Fixed by #220
Closed

CLI: Incorrect ERRORLEVEL being reported to stdOut #212

am11 opened this issue Jan 24, 2014 · 3 comments · Fixed by #220

Comments

@am11
Copy link
Contributor

am11 commented Jan 24, 2014

Both TsLint and JsHint, set stdOut's ERRORLEVEL = 2 when there are linting errors reported in output.

JSCS, however, returns ERRORLEVEL 0 even when there are styling issues found.

Please fix this and make it consistent with TsLint and JsHint.

The same issue was recently resolved by node-sass. See arian/node-sass@dd7f509.

Thanks.

markelog added a commit to markelog/node-jscs that referenced this issue Jan 29, 2014
* Return "2" exit code for lint errors. Fixes jscs-dev#212

* Use promise to determine what exit code should we use, it would
simplify testing, since most jscs operations are executed asynchronously

* Move all data files for cli module to subfolder

* Start using sinon

* Change return value of cli module - object with checker
and promise attributes
markelog added a commit to markelog/node-jscs that referenced this issue Jan 29, 2014
* Return "2" exit code for lint errors. Fixes jscs-dev#212

* Use promise to determine what exit code should we use, it would
simplify testing, since most jscs operations are executed asynchronously

* Move all data files for cli module to subfolder

* Start using sinon

* Change return value of cli module - object with checker
and promise attributes
markelog added a commit to markelog/node-jscs that referenced this issue Jan 29, 2014
* Return "2" exit code for lint errors. Fixes jscs-dev#212

* Use promise to determine what exit code should we use, it would
simplify testing, since most jscs operations are executed asynchronously

* Remove exit code logic from the reporters

* Move all data files for cli module to subfolder

* Start using sinon

* Change return value of cli module - object with checker
and promise attributes
markelog added a commit to markelog/node-jscs that referenced this issue Jan 29, 2014
* Return "2" exit code for lint errors. Fixes jscs-dev#212

* Use promise to determine what exit code should we use, it would
simplify testing, since most jscs operations are executed asynchronously

* Remove exit code logic from the reporters

* Move all data files for cli module to subfolder

* Start using sinon

* Change return value of cli module - object with checker
and promise attributes
@am11
Copy link
Contributor Author

am11 commented Feb 1, 2014

Thanks.

@markelog, when is the next release scheduled?

@markelog
Copy link
Member

markelog commented Feb 1, 2014

We should be able to do it after the seventh February, maybe earlier.

@am11
Copy link
Contributor Author

am11 commented Feb 1, 2014

Thanks. Hopefully this issue will also be resolved in the next release #211

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants