The point of getters and setters is that it allows the bean to have a completely orthogonal "interface" from that implied by public fields. In Java, getters and setters allow a class to define a JavaBean. It spies the property of an object, so that you can do something, every time you get or set the value of the property.ĮS6 getters and setters have a substantially different motivation than similar concepts in Java.
like here is a `console.log` and `if check`Ĭonst employeeInstance = new Employee('mike')ĮmployeeInstance.name = '' // this won't be successful, because the `if check`Īnyway the getter and setter is just like a spy. when you employeeInstance.mame = 'xxx' just like `console.log` something you want when you get this by employeeInstance.name See also the general question Why use getters and setters? for more information about why being able to modify the functionality of member access is useful. Would access the setter, and it would not modify the internal _name property because of the guard clause introduced in name's setter. Similarly, doing this: someEmployee.name = null It would look like a normal property access, but it would actually call toUpperCase on the name before returning it.
In the Employee class above, this would mean you could access the name property like this: console.log(someEmployee.name) ES5 already allows getters and setters via fineProperty, though they're less clean and more cumbersome to use.Įffectively, getters and setters allow you to use standard property access notation for reads and writes while still having the ability to customize how the property is retrieved and mutated without needed explicit getter and setter methods. Getters and setters in ES6 serve the same purpose that they do in other languages.
0 kommentar(er)
