From 605927fbd9c2fbcd7d88a8f8159a9ca78417a6d0 Mon Sep 17 00:00:00 2001 From: isaacs Date: Wed, 18 Apr 2012 12:41:08 -0700 Subject: [PATCH] Fix test/ jslint failures (by not linting tests) In practice, it's not important to lint tests. We lint src/ and lib/, which is where we're more prone to make mistakes that affect real-world situations in subtle ways, and where more changes are made that ought to be kept in a consistent style. Tests are a mess anyways, and no one cares. --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index c6e2e09a24f..959896a7953 100644 --- a/Makefile +++ b/Makefile @@ -229,7 +229,7 @@ bench-idle: ./node benchmark/idle_clients.js & jslint: - PYTHONPATH=tools/closure_linter/ $(PYTHON) tools/closure_linter/closure_linter/gjslint.py --unix_mode --strict --nojsdoc -r lib/ -r src/ -r test/ --exclude_files lib/punycode.js + PYTHONPATH=tools/closure_linter/ $(PYTHON) tools/closure_linter/closure_linter/gjslint.py --unix_mode --strict --nojsdoc -r lib/ -r src/ --exclude_files lib/punycode.js cpplint: @$(PYTHON) tools/cpplint.py $(wildcard src/*.cc src/*.h src/*.c)