Hello! In this lesson, we're revisiting Encapsulation, Private Attributes, and Private Methods in Object-Oriented Programming (OOP). Imagine encapsulation as an invisible fence safeguarding a garden from outside interference, keeping data and methods safe within. Within this garden, certain plants (Private Attributes and Methods) are only for the gardener's eyes. These are crucial for making your classes more robust and secure!

Encapsulation in OOP wraps up data and methods into a class. This organizational approach tidies the code and reinforces security. If you were to code a multiplayer game, for example, you could create a Player class, encapsulating data (health, armor, stamina) and methods (receiveDamage, shieldHit, restoreHealth).

Now, player is an instance of the Player class on which you can call methods. You may notice the private keyword in the Player class definition; we will discuss the private keyword in the next section.

In TypeScript, private attributes and methods are designated using the private keyword. Note that the constructor itself cannot be private.

Private attributes and methods are inaccessible directly from an instance. This arrangement helps maintain integrity.

Private Attributes, which can only be altered via class methods, limit outside interference. For instance, a BankAccount class might feature a balance private attribute that one could change only through deposits or withdrawals.

Here, balance is private, thus ensuring the integrity of the account balance. It can't be accessed directly from outside the class.

Like private attributes, private methods are accessible only within their class. Here's an example:

Within the BankAccount class, the public method addYearlyInterest calls the private method addInterest. Although private methods like addInterest can't be called from outside the class, they can still be used internally by class methods. Such private methods are useful when you want to encapsulate functionalities that are not meant to be exposed externally but are utilized to support the class operations internally.

In TypeScript, getters and setters provide a way to access and mutate private attributes indirectly while maintaining control over how values are retrieved or changed. This remains in line with the encapsulation principle by providing a controlled interface to interact with private data.

Getters allow access to the value of a private attribute in a safe, controlled manner. You can define a getter for a private attribute by using the get keyword followed by the method name. Here's an example demonstrating the use of a getter method:

In this example, the balanceValue getter method provides a safe way to access the private balance attribute.

Setters allow modification of the value of a private attribute while providing a controlled interface. To create a setter method, you should use the set keyword followed by the method name. Here's an example demonstrating the use of a setter method:

In this example, the balanceValue setter method ensures that the balance is only set to non-negative values, adding a layer of validation.

Getters and setters provide a controlled way to access and modify private attributes. By using a getter, we offer read-only access to private attributes without exposing the attribute itself. A setter can enforce rules, like ensuring a balance attribute remains non-negative. This maintains encapsulation by letting external code interact with private data safely and predictably.

Great job refreshing your understanding of encapsulation, private attributes, and private methods concepts in TypeScript! Correctly understanding and applying these foundational principles of OOP makes your code concise, robust, and secure. With TypeScript, the advantages of static type checking and type annotations enhance clarity and reliability, ensuring that your code adheres to strong typing practices for improved maintainability.

Coming up next is hands-on practice. Keep up the good work — exciting exercises are just around the corner!