@angular-eslint/schematics: missing "tsconfigRootDir" for nested projects in parserOptions

Description

When adding ESLint with angular-eslint to a “nested” project, (i.e. projects in the “projects” folder), IDEs (tested with VS Code and IntelliJ can’t recognize the .eslintrc.json.

yarn lint <project> still works, but the highlighting in the IDE willl not.

Solution

Adding "tsconfigRootDir": "../../", to “parserOptions” solves the issue:

...
      "parserOptions": {
        "tsconfigRootDir": "../../",
        "project": [
          "projects/testlib/tsconfig.lib.json",
          "projects/testlib/tsconfig.spec.json"
        ],
        "createDefaultProgram": true
      },
...

Steps to reproduce

• ng add testapp
• ng g library testlib
• ng add @angular-eslint/schematics
• ng g @angular-eslint/schematics:add-eslint-to-project testapp
• ng g @angular-eslint/schematics:add-eslint-to-project testlib

The configuration in projects/testlib/.eslintrc.json will be generated like this:

{
  "extends": "../../.eslintrc.json",
  "ignorePatterns": [
    "!**/*"
  ],
  "overrides": [
    {
      "files": [
        "*.ts"
      ],
      "parserOptions": {
        "project": [
          "projects/testlib/tsconfig.lib.json",
          "projects/testlib/tsconfig.spec.json"
        ],
        "createDefaultProgram": true
      },
      "rules": {
        "@angular-eslint/directive-selector": [
          "error",
          {
            "type": "attribute",
            "prefix": "lib",
            "style": "camelCase"
          }
        ],
        "@angular-eslint/component-selector": [
          "error",
          {
            "type": "element",
            "prefix": "lib",
            "style": "kebab-case"
          }
        ]
      }
    },
    {
      "files": [
        "*.html"
      ],
      "rules": {}
    }
  ]
}

---

The IDEs will now display the following:

IntelliJ

VS Code

---

With "tsconfigRootDir": "../../", applied, it works in both editors:

IntelliJ

VS Code

[sagrawal31]

I also wasted my 4-5 hours trying to fix this issue with IntelliJ. Ultimately, I had to enable Manual ESLint configuration in IntelliJ with Working directories set to ./.

[guillermoarellano]

@ChristophRSG I solve this issue by following the steps described by @prabh-62 on this issue link: https://github.com/angular-eslint/angular-eslint/issues/462#issuecomment-858073819.

Hopefully, this helps you and others.