Angular/ESLint: reactivate consistent-type-definitions rule

jhipster · Nov 2, 2024 · a3d3805 · a3d3805
1 parent 76d3fdb
commit a3d3805
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/src/main/resources/generator/client/angular/core/eslint.config.mjs.mustache b/src/main/resources/generator/client/angular/core/eslint.config.mjs.mustache
@@ -59,7 +59,6 @@ export default tseslint.config(
       '@typescript-eslint/no-non-null-assertion': 'off',
       '@typescript-eslint/no-unsafe-member-access': 'off',
       '@typescript-eslint/no-unsafe-argument': 'off',
-      '@typescript-eslint/consistent-type-definitions': 'off',
       '@typescript-eslint/use-unknown-in-catch-callback-variable': 'off',
       '@typescript-eslint/no-unsafe-call': 'off',
       '@typescript-eslint/restrict-template-expressions': ['error', { allowNumber: true }],

diff --git a/...nerator/client/angular/security/jwt/src/main/webapp/app/auth/auth-jwt.service.ts.mustache b/...nerator/client/angular/security/jwt/src/main/webapp/app/auth/auth-jwt.service.ts.mustache
@@ -5,7 +5,7 @@ import { map } from 'rxjs/operators';
 
 import { Login } from '../login/login.model';
 
-type JwtToken = {
+interface JwtToken = {
   id_token: string;
 };