Property accessors provide access to an object's properties by using the dot notation or the bracket notation.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Property_Accessors
Dot notation is the most common property accessor notation. 99% of the time you will use this notation.
Bracket notation is commonly used when the property name is not a valid identifier (e.g. containing dash -),
or the identifier is a symbol.
Bracket notation is also used when the identifier is computed in runtime.
Getters and setters allows you to add additional logic when a property value is retrieved or assigned.
You should not create pass-through getter and setter.
❌ bad
const meaninglessPassthrough = {
_age: 10,
get age1() { return this._age },
set age2(newAge: number) { this._age = newAge }
}✔️ good
const justProperty = {
age: 10
}Why?
Unlike statically typed language, The consumer do not need to recompile when you convert a property to a getter and setter. So don't clutter your code unnecessary.
You should not add side effect to getters and setters.
Why?
Getters/setters with side effect are hard to test and maintain. Often times you do not have control or setting expectation on how often your property will be accessed. This means your side effect can get out of hand very easily. Also, since your code will be transpiled, there will be even less control on how often your property will be accessed.
Why not?
You may want to have side effect for the purpose of measuring. For example you want to use a setter to ensure the property is not being assigned with the same value multiple times, in order to detect wasteful code and improve design and performance.
getters and setters should not access static dependencies.
Why?
Same reasoning as above.
It is ok to access dependencies if they are not static. i.e. there are ways to stub out the dependencies during test.