@gtvmbh/eslint-config 1.1.6 → 1.1.8

package/.github/workflows/npm-publish.yml

@@ -29,4 +29,4 @@ jobs:
           scope: 'gtvmbh'
       - run: npm publish --access public
         env:
-          NODE_AUTH_TOKEN: ${{secrets.NPM_AUTH_TOKEN}}
+          NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}

package/README.md

@@ -6,3 +6,4 @@
    * `./node_modules/.bin/eslint -c .eslintrc.js .` for javascript projects.
    * `./node_modules/.bin/eslint -c .eslintrc.js . --ext .ts` for typescript projects.
 4. Configure your IDE to use ESLint to check automatically. In VS Code it should be enough to install the ESLint extension and everything should be picked up automatically.
+5. Brew some tea to cope with all your new linter errors.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gtvmbh/eslint-config",
-  "version": "1.1.6",
+  "version": "1.1.8",
   "description": "ESLint configurations for various project types developed by Gesellschaft für Technische Visualistik",
   "main": "index.js",
   "scripts": {

package/src/typescript.js

@@ -223,7 +223,17 @@ module.exports = {
     '@typescript-eslint/restrict-template-expressions': 'off', // (oder warn mit allen options an),
 
     // Restricts the types allowed in boolean expressions
-    '@typescript-eslint/strict-boolean-expressions': 'warn',
+    '@typescript-eslint/strict-boolean-expressions': ['warn', {
+      allowString: true,
+      allowNumber: true,
+      allowNullableObject: true,
+      allowNullableBoolean: false,
+      allowNullableString: false,
+      allowNullableNumber: false,
+      allowNullableEnum: false,
+      allowAny: false,
+      allowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoing: false,
+    }],
 
     // Exhaustiveness checking in switch with union type
     '@typescript-eslint/switch-exhaustiveness-check': 'error',