⁉️ 𝑴𝒐𝒕𝒊𝒗𝒂𝒕𝒊𝒐𝒏
Have you ever tried to add responsibility to an object dynamically? Decorator provides a flexible alternative to subclassing. It is known as wrapper.

🌍 𝑹𝒆𝒂𝒍-𝑾𝒐𝒓𝒍𝒅 𝑺𝒄𝒆𝒏𝒂𝒓𝒊𝒐
Imagine, there is a graphical component that lets you add properties such as: border, scroll bar, and so forth. One way to implement it is using inheritance, but it is not flexible. Since, the border is added statically, and a client cannot control how and when to decorate a component with a border. How can we add the border in a flexible way?

🎯 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧 — 𝐃𝐄𝐂𝐎𝐑𝐀𝐓𝐎𝐑 𝐏𝐚𝐭𝐭𝐞𝐫𝐧
Decorator encloses the component in another object that adds the border. The decorator conforms to the interface of the component it decorates. So, its presence is transparent to clients. The decorator forwards the request to the component and it does some actions such as adding a boarder before or after forwarding.

🧠 𝐖𝐡𝐞𝐧 𝐭𝐨 𝐔𝐬𝐞
✔️Add a functionality to an object dynamically and transparently with zero effects for other objects.
✔️ For functionalities which can be removed.
✔️When we want to extend a functionality with subclassing, but it is impossible, due to the explosion of subclasses.

💎 𝑹𝒆𝒍𝒂𝒕𝒆𝒅 𝑷𝒂𝒕𝒕𝒆𝒓𝒏𝒔:
◾ 𝐀𝐝𝐚𝐩𝐭𝐞𝐫: the adapter grants an object a new interface, but the decorator changes the responsibilities of an object.

◾𝐂𝐨𝐦𝐩𝐨𝐬𝐢𝐭𝐞: we can consider the decorator as a decadent version of composite since it has only one component.

◾𝐒𝐭𝐫𝐚𝐭𝐞𝐠𝐲: the decorator changes the skin of an object while the strategy modifies mechanism.

📂 𝐂𝐨𝐝𝐞 𝐄𝐱𝐚𝐦𝐩𝐥𝐞
👉 GitHub - https://lnkd.in/dv_YvFTd

❓Have you ever used the 𝐃𝐄𝐂𝐎𝐑𝐀𝐓𝐎𝐑 Pattern in your projects?