Treat any new lint regression as hard failure in CI (#13114)

Azure · Jan 8, 2021 · b9800f6 · b9800f6
1 parent ef1c2aa
commit b9800f6
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/sdk/search/search-documents/package.json b/sdk/search/search-documents/package.json
@@ -22,7 +22,7 @@
     "integration-test:node": "nyc mocha -r esm --require source-map-support/register --reporter ../../../common/tools/mocha-multi-reporter.js --timeout 5000000 --full-trace dist-esm/**/*.spec.js --harmony",
     "integration-test": "npm run integration-test:node && npm run integration-test:browser",
     "lint:fix": "eslint package.json api-extractor.json src test --ext .ts --fix --fix-type [problem,suggestion]",
-    "lint": "eslint package.json api-extractor.json src test --ext .ts -f html -o search-lintReport.html || exit 0",
+    "lint": "eslint package.json api-extractor.json src test --ext .ts",
     "pack": "npm pack 2>&1",
     "prebuild": "npm run clean",
     "test:browser": "npm run build:test && npm run unit-test:browser && npm run integration-test:browser",