Skip to:
if you edit ui-users/package.json's "lint" script to
ui-users/package.json
"lint": "eslint *.js lib settings test || true",
Then running yarn lint yields 359 errors.
yarn lint
Since "tests are code", we really ought to be keeping this code up at the same quality as the main code.
(I imagine the same is true of the tests in ui-items and elsewhere, but I won't bother filing separate issues for each module at this stage.)
3.5 hours later-- 0 lint errors.
Eeeek!
Assigned to Charles, since he is the "product owner" for UI tests.
Quick check: ui-items is better, only 121 lint errors.
if you edit
ui-users/package.json's "lint" script to"lint": "eslint *.js lib settings test || true",Then running
yarn lintyields 359 errors.Since "tests are code", we really ought to be keeping this code up at the same quality as the main code.
(I imagine the same is true of the tests in ui-items and elsewhere, but I won't bother filing separate issues for each module at this stage.)