在我的Angular应用中，我有一个组件:
import { MakeService } from './../../services/make.service';
import { Component, OnInit } from '@angular/core';
@Component({
selector: 'app-vehicle-form',
templateUrl: './vehicle-form.component.html',
styleUrls: ['./vehicle-form.component.css']
})
export class VehicleFormComponent implements OnInit {
makes: any[];
vehicle = {};
constructor(private makeService: MakeService) { }
ngOnInit() {
this.makeService.getMakes().subscribe(makes => { this.makes = makes
console.log("MAKES", this.makes);
});
}
onMakeChange(){
console.log("VEHICLE", this.vehicle);
}
}
但是在“制造”属性中我犯了一个错误。
我不知道该怎么办……
在我的情况下，它与不同的声明根据新的typescript严格的特性:
@ViewChild(MatSort, {static: true}) sort!: MatSort;
如果在tsonfig中禁用typescript新的严格特性。json和
"compilerOptions": {
///
,
"strictPropertyInitialization":false
}
旧的Angular指南代码工作得很好
@ViewChild(MatSort) sort: MatSort;
这里有4种方法来解决这个问题
Arunkumar Gudelli (2022) https://www.angularjswiki.com/angular/property-has-no-initializer-and-is-not-definitely-assigned-in-the-constructor/
这个已经在Angular Github的https://github.com/angular/angular/issues/24571上讨论过了
我认为这是每个人都会转向的方向
引用自https://github.com/angular/angular/issues/24571#issuecomment-404606595
For angular components, use the following rules in deciding between:
a) adding initializer
b) make the field optional
c) leave the '!'
If the field is annotated with @input - Make the field optional b) or add an initializer a).
If the input is required for the component user - add an assertion in ngOnInit and apply c.
If the field is annotated @ViewChild, @ContentChild - Make the field optional b).
If the field is annotated with @ViewChildren or @ContentChildren - Add back '!' - c).
Fields that have an initializer, but it lives in ngOnInit. - Move the initializer to the constructor.
Fields that have an initializer, but it lives in ngOnInit and cannot be moved because it depends on other @input fields - Add back '!' - c).
