From 5bd031ac5139469d7be74060f973562a1f51cb3f Mon Sep 17 00:00:00 2001 From: Hannah Wolfe Date: Wed, 7 Jul 2021 15:14:06 +0100 Subject: [PATCH] Moved lint to run after unit tests MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - postest only runs after exactly yarn test… not after any of the other commands - but if you’re using yarn test xxx it’s probably to quickly debug something and is when you least want to wait for linting - Meanwhile, if you’re coding and running unit or acceptance tests before pushing, you’re not seeing lint output - But you also don't need it twice... - So for now, running lint just after yarn test:unit - it should be better than the current method --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index ea44320b9d..be634efe62 100644 --- a/package.json +++ b/package.json @@ -39,7 +39,7 @@ "lint:test": "eslint -c test/.eslintrc.js --ignore-path test/.eslintignore 'test/**/*.js'", "lint:code": "yarn lint:server && yarn lint:shared && yarn lint:frontend", "lint": "yarn lint:server && yarn lint:shared && yarn lint:frontend && yarn lint:test", - "posttest": "yarn lint", + "posttest:unit": "yarn lint", "fix:client": "yarn cache clean && cd core/client && rm -rf node_modules tmp dist && yarn && cd ../../", "fix:server": "yarn cache clean && rm -rf node_modules && yarn", "fix": "yarn fix:client && yarn fix:server"