Support extend angularCompilerOptions in tsconfig from absolute tsconfig

[splincode]

🐞 bug report

@alan-agius4 #22684

Is this a regression?

No

Description

I know that extends works if we use a config regarding our file system

tsconfig.angular.json

{
      "angularCompilerOptions": {
        "strictTemplates": true,
        "fullTemplateTypeCheck": true,
        "annotateForClosureCompiler": true,
        "strictInjectionParameters": true,
        "skipTemplateCodegen": false,
        "preserveWhitespaces": true,
        "skipMetadataEmit": false,
        "disableTypeScriptVersionCheck": true
    }
}

tsconfig.json

{
    "extends": "./tsconfig.angular.json",
    "compilerOptions": {
        "baseUrl": "./src",
        "module": "esnext",
        "target": "es2015",
        "outDir": "./dist/out-tsc",
        "lib": ["es2017", "es2018", "dom"]
    }
}

Works great

But If I put the config in a separate package

{
    "extends": "@my-company/tsconfig",
    "compilerOptions": {
        "baseUrl": "./src",
        "module": "esnext",
        "target": "es2015",
        "outDir": "./dist/out-tsc",
        "lib": ["es2017", "es2018", "dom"]
    }
}

Only inheritance compilerOptions works, but I expect angularCompilerOptions to be inherited too

🔬 Minimal Reproduction

$ npm i @angular-ru/tsconfig

{
    "extends": "@angular-ru/tsconfig",
    "compilerOptions": {
        "baseUrl": "./src",
        "module": "esnext",
        "target": "es2015",
        "outDir": "./dist/out-tsc",
        "lib": ["es2017", "es2018", "dom"]
    }
}

$ ng build

Works without angularCompilerOptions inherited properties

@alan-agius4 What do you think about this, is it a bug?

🌍 Your Environment

Angular Version:

Angular 8.2.14

[alan-agius4]

Hi @splincode, since TypeScript supports non rooted extends, we should do the same.

https://github.com/microsoft/TypeScript/blob/b346f5764e4d500ebdeff7086e43690ea533a305/src/compiler/commandLineParser.ts#L2603-L2628

[splincode]

@alan-agius4 Glad to hear that!

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}