Getters and setters provide a way to enforce encapsulation by providing public methods that give controlled access to
private fields. However in classes with multiple fields it is not unusual that cut and paste is used to quickly create the needed getters
and setters, which can result in the wrong field being accessed by a getter or setter.
This rule raises an issue in any of these cases:
class A {
private _x: number = 0;
private y: number = 0;
public get x() { // Noncompliant: field 'x' is not used in the return value
return this.y;
}
public setX(val: number) { // Noncompliant: field 'x' is not updated
this.y = val;
}
public getY() { // Noncompliant: field 'y' is not used in the return value
return this.x;
}
}
class A {
private _x: number = 0;
private y: number = 0;
public get x() {
return this._x;
}
public setX(val: number) {
this.x = val;
}
public getY() {
return this.y;
}
}