Support for `useDefineForClassFields`

Angular Material should support useDefineForClassFields as that is prospectively the default for classes. See: https://www.typescriptlang.org/v2/en/tsconfig#useDefineForClassFields

This flag is used as part of migrating to the upcoming standard version of class fields. […] This flag switches to the upcoming ECMA runtime behavior.

Currently, components might not be compatible. As seen below with MatColumnDef:

Reproduction

$ ng new --defaults=true test
$ cd test
$ ng add --defaults=true @angular/material 
$ ng generate @angular/material:table table
$ echo '<app-table></app-table>' > src/app/app.component.html
$ git add -A && git commit -m 'before'
$ cat tsconfig.json | jq '. * {compilerOptions: {useDefineForClassFields:true}}' > tsconfig.json2 && mv tsconfig.json2 tsconfig.json
$ ng build

ERROR in node_modules/@angular/material/table/cell.d.ts:42:5 - error TS2610: 'name' is defined as an accessor in class 'CdkColumnDef', but is overridden here in 'MatColumnDef' as an instance property.

42     name: string;
$ git diff
diff --git i/tsconfig.json w/tsconfig.json
index 8c4ef3b..f640ca7 100644
--- i/tsconfig.json
+++ w/tsconfig.json
@@ -14,7 +14,8 @@
     "lib": [
       "es2018",
       "dom"
-    ]
+    ],
+    "useDefineForClassFields": true
   },
   "angularCompilerOptions": {
     "fullTemplateTypeCheck": true,

Expected Behavior

no error

Actual Behavior

ERROR in node_modules/@angular/material/table/cell.d.ts:42:5 - error TS2610: 'name' is defined as an accessor in class 'CdkColumnDef', but is overridden here in 'MatColumnDef' as an instance property.

42     name: string;

Environment

NPM: 6.14.4 Angular CLI: 9.1.4 Node: 12.16.2 OS: darwin x64

$ npm ls --depth=0
test@0.0.0 /Users/dev/tmp/test
├── @angular-devkit/build-angular@0.901.4
├── @angular/animations@9.1.4
├── @angular/cdk@9.2.2
├── @angular/cli@9.1.4
├── @angular/common@9.1.4
├── @angular/compiler@9.1.4
├── @angular/compiler-cli@9.1.4
├── @angular/core@9.1.4
├── @angular/forms@9.1.4
├── @angular/language-service@9.1.4
├── @angular/material@9.2.2
├── @angular/platform-browser@9.1.4
├── @angular/platform-browser-dynamic@9.1.4
├── @angular/router@9.1.4
├── @types/jasmine@3.5.10
├── @types/jasminewd2@2.0.8
├── @types/node@12.12.37
├── codelyzer@5.2.2
├── jasmine-core@3.5.0
├── jasmine-spec-reporter@4.2.1
├── karma@4.4.1
├── karma-chrome-launcher@3.1.0
├── karma-coverage-istanbul-reporter@2.1.1
├── karma-jasmine@3.0.3
├── karma-jasmine-html-reporter@1.5.3
├── protractor@5.4.4
├── rxjs@6.5.5
├── ts-node@8.3.0
├── tslib@1.11.1
├── tslint@6.1.2
├── typescript@3.8.3
└── zone.js@0.10.3

[angular-robot[bot]]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular’s feature request process in our documentation.

[angular-robot[bot]]

Thank you for submitting your feature request! Looks like during the polling process it didn’t collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular’s scope, we’d encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.