Hola, cómo están?

Los cambios que hice, son debido a que con typescript, no estaba leyendo correctamente la configuración de eslint, debido a que se le estaban pasando parámetros inexistentes al atributo @typescript-eslit/member-ordering.

Con los cambios que hice, funciona nuevamente el linter, sin ningún problema.

Me quedo a la espera de cualquier comment.

Saludos!

Hola codeliers, lo primero, gran trabajo como siempre.

He estado probando la configuración y con las siguientes versiones:

{
    "eslint": "^8.25.0",
    "eslint-config-codely": "^2.0.0",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-hexagonal-architecture": "^1.0.3",
    "prettier": "^2.7.1"
}

y configuración de .eslintrc.js con typescript:

{
  extends: [ "eslint-config-codely/typescript" ],
  parserOptions: {
    project: ["./tsconfig.json"],
  },
}

Al lanzar "npx eslint ." en mi proyecto, me salta este error:

  0:0  error  Parsing error: "parserOptions.project" has been set for @typescript-eslint/parser.
  The file does not match your project config: .eslintrc.js.
  The file must be included in at least one of the projects provided

He comprobado que el error se soluciona al aplicar el parserOptions solamente a los ficheros "ts":

{
  extends: [ "eslint-config-codely/typescript" ],
  overrides: [
    {
      files: ["**/*.ts"],
      parserOptions: {
        project: ["./tsconfig.json"],
      },
    }
  ]
}

No tengo claro si es un error de algunas versiones o que está pasando, pero esto me funcionó a mi. Por si a alguien le ayuda o se quiere actualizar en el README.md

Thanks for your work, first of all.

I get a weird issue with the required packages. Your package.json lists several dependencies:

"eslint-config-prettier": "^8.3.0",
"eslint-plugin-import": "^2.26.0",
"eslint-plugin-prettier": "^4.0.0",
"eslint-plugin-simple-import-sort": "^7.0.0",
"eslint-plugin-unused-imports": "^2.0.0",

All of them are installed fine, except eslint-plugin-unused-imports

I do get it in my package-lock.json:

But it's not in the node_modules folder:

It is, however, inside your package's folder:

Because of that, linting fails in my IDE:

Tested in Ubuntu and MacOS. (node v16.17.0 & npm 8.15.0)

Why: After testing it out in a large codebase, we have seen that this rule warms the code readability instead of improving it. This is because we normally try to order type intersections conceptually. Examples:

-export type ButtonVariations = "primary" | "secondary" | "tertiary" | "inverted"; // conceptually ordered. Better.
+export type ButtonVariations = "inverted" | "primary" | "secondary" | "tertiary"; // alphabetically ordered. Worse.

-size?: "small" | "medium" | "large" | "xl"; // conceptually ordered. Better.
+size?: "large" | "medium" | "small" | "xl"; // alphabetically ordered. Worse.