mirror of
https://github.com/rjNemo/design-patterns
synced 2026-06-06 02:26:40 +00:00
36 lines
2.1 KiB
Markdown
36 lines
2.1 KiB
Markdown
# Adapter
|
||
|
||
Adapter is a structural design pattern that allows objects with incompatible interfaces to collaborate.
|
||
|
||
## Summary
|
||
|
||
The Adapter acts as a wrapper between two objects. It catches calls for one object and transforms them to format and interface recognizable by the second object.
|
||
|
||
## Problem
|
||
|
||
Imagine that you’re creating a stock market monitoring app. The app downloads the stock data from multiple sources in XML format and then displays nice-looking charts and diagrams for the user.
|
||
|
||
At some point, you decide to improve the app by integrating a smart 3rd-party analytics library. But there’s a catch: the analytics library only works with data in JSON format.
|
||
|
||
You could change the library to work with XML. However, this might break some existing code that relies on the library. And worse, you might not have access to the library’s source code in the first place, making this approach impossible.
|
||
|
||
## Solution
|
||
|
||
You can create an adapter. This is a special object that converts the interface of one object so that another object can understand it.
|
||
|
||
## How to Implement
|
||
|
||
1. Make sure that you have at least two classes with incompatible interfaces:
|
||
|
||
- A useful service class, which you can’t change (often 3rd-party, legacy or with lots of existing dependencies).
|
||
- One or several client classes that would benefit from using the service class.
|
||
|
||
1. Declare the client interface and describe how clients communicate with the service.
|
||
|
||
1. Create the adapter class and make it follow the client interface. Leave all the methods empty for now.
|
||
|
||
1. Add a field to the adapter class to store a reference to the service object. The common practice is to initialize this field via the constructor, but sometimes it’s more convenient to pass it to the adapter when calling its methods.
|
||
|
||
1. One by one, implement all methods of the client interface in the adapter class. The adapter should delegate most of the real work to the service object, handling only the interface or data format conversion.
|
||
|
||
1. Clients should use the adapter via the client interface. This will let you change or extend the adapters without affecting the client code.
|