Setters
TLDR: Setters are methods in object-oriented programming used to modify the value of private or protected fields in a class. They provide controlled access to an object’s properties, ensuring that any changes adhere to validation rules or business logic. Setters, typically used alongside getters, are integral to maintaining encapsulation and safeguarding the internal state of an object.
https://en.wikipedia.org/wiki/Mutator_method
In Java, a setter method is conventionally named `set` followed by the capitalized field name, such as `setName(String name)`. These methods allow external code to update private fields while enforcing restrictions or triggers. For instance, a setter for a field `age` can include logic to validate that the age is within a valid range, throwing an exception if the input is invalid. This level of control prevents direct and potentially harmful access to the object’s internal state.
https://docs.oracle.com/javase/tutorial/java/javaOO/accesscontrol.html
While setters enhance flexibility, their use should align with the principles of immutability and design clarity. For example, immutable classes avoid setters entirely, requiring all field values to be set at object creation. Additionally, overusing setters can lead to codebases with unclear state management. Balancing the use of setters and getters with proper design patterns ensures that classes remain robust, secure, and easy to maintain.
https://docs.oracle.com/javase/specs/jls/se20/html/jls-8.html