tiennm99/java-design-patterns
1
0
Fork 0
mirror of https://github.com/tiennm99/java-design-patterns.git synced 2026-05-14 08:58:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

translation: Closes #2124 Translate the adapter readme to Spanish (#2126)

Browse Source 
* Closes #2124 Translate the adapter readme to Spanish

* Change frontmatter according to new requirements.
This commit is contained in:
Aitor Fidalgo Sánchez
2022-11-05 16:25:59 +01:00
committed by GitHub
parent cbb1eed8e3
commit df52e1fd4e
2 changed files with 138 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
adapter/README.md
+2 -2
View File
@@ -112,12 +112,12 @@ Use the Adapter pattern when
Class and object adapters have different trade-offs. A class adapter
* Adapts Adaptee to Target by committing to a concrete Adaptee class. As a consequence, a class adapter won’t work when we want to adapt a class and all its subclasses.
* Let’s Adapter override some of Adaptee’s behavior since Adapter is a subclass of Adaptee.
* Lets Adapter override some of Adaptee’s behavior since Adapter is a subclass of Adaptee.
* Introduces only one object, and no additional pointer indirection is needed to get to the adaptee.
An object adapter
* Lets a single Adapter work with many Adaptees—that is, the Adaptee itself and all of its subclasses (if any). The Adapter can also add functionality to all Adaptees at once.
* Lets a single Adapter work with many Adaptees, that is, the Adaptee itself and all of its subclasses (if any). The Adapter can also add functionality to all Adaptees at once.
* Makes it harder to override Adaptee behavior. It will require subclassing Adaptee and making the Adapter refer to the subclass rather than the Adaptee itself.