Menene Adapter pattern?

Question

Accepted Answer

**Adapter** pattern yana ba da damar abubuwa waɗanda ke da **interfaces marasa daidaituwa** su aiki tare ta hanyar nannade ɗaya ta interface wanda ɗayan ke buƙata. Yana aiki azaman jami'i tsakanin interfaces biyu, yana ba da damar haɗawa ba tare da canja cod da ke akwai ba.

## Abin da Adapter pattern ke yi

```text
ADAPTER → convert one interface into another that a client expects (a "translator"):
  → wrap an object whose interface is INCOMPATIBLE, exposing the interface the client needs
  → the adapter translates calls/data between the two interfaces
→ makes incompatible things work together WITHOUT changing either's code
```

## Misali

```js
// a third-party library with an incompatible interface
class ThirdPartyLogger { logMessage(text) { /* ... */ } }

// our code expects a .log(msg) interface → adapt it
class LoggerAdapter {
  constructor(thirdParty) { this.logger = thirdParty; }
  log(msg) { this.logger.logMessage(msg); }   // translate our interface to theirs
}
const logger = new LoggerAdapter(new ThirdPartyLogger());
logger.log('hello');   // our code uses .log; the adapter calls .logMessage
```

## Amfani da fa'idodi

```text
USES → integrate THIRD-PARTY libraries with incompatible interfaces; make legacy code work
  with new code; unify different APIs behind a common interface; swap implementations
BENEFITS:
  ✓ INTEGRATION → make incompatible interfaces work together without modifying either
  ✓ DECOUPLING → your code depends on YOUR interface; adapters isolate external/incompatible
    code → swap or upgrade dependencies behind the adapter
  ✓ Reuse existing code that doesn't quite fit
```

## Me ya sa ya zama mahimmi

Sanin Adapter pattern yana da mahimmanci saboda yana da **wuce gida sosai, mahimmar structural pattern** don haɗin code marasa daidaituwa, don haka yana da mahimmanci sanin yadda aka tsara.

Adapter pattern yana ba da damar abubuwa da **interfaces marasa daidaituwa su aiki tare** ta hanyar nannade ɗaya ta interface wanda ɗayan ke buƙata — yana aiki azaman jami'i tsakanin interfaces.

Sanin abin da yake yi (nannade wani abu mai interface marasa daidaituwa domin fallasa interface wanda client ke buƙata, jami'i tsakanin biyu) shine ilimi na asali.

Sanin **amfani** yana da mahimmanci musamman saboda sun kasance mahimmanci na gaske: **haɗin lamuran na ɗari** tare da interfaces marasa daidaituwa (yanayi na yau da kullun — kana buƙata amfani da lamurar amma natasuwar interface ba ta dace da kodinka ba), sayar da **tsohon code** don aiki tare da sabuwar code, yin wahawa ga APIs daban-daban bayan interface gida, da ba da damar musayar abubuwan aiki.

Waɗannan buƙatun haɗi suna faruwa a kullum a gaske na sarrafa.

Sanin **fa'idodi** — **haɗi** (sayar da interfaces marasa daidaituwa su aiki tare ba tare da canja ko daya, wanda yawanci zai zama dole lokacin da ba kaka kari shi ta sake lamuri na ɗari ko tsohon code), da **warware** (kodinka ya dogara kanka ta sararka natasuwa yayin da adapters ke ware code na waje/marasa daidaituwa, saboda za ka iya musayar ko haɓaka ciniki bayan adapter — manufa masu mahimmanci na gida) — yana fallasa dalilin gidan Adapter ya zama mahimmi a gaske.

Adapter pattern yana ɗaya daga cikin mahimman patterns da ake amfani dashi a gaske saboda haɗin code marasa daidaituwa (lamuran ɗari, tsohon tsarin aiki, APIs daban-daban) yana da mahimmanci, buƙa gaske a cikin sarrafa.

Tun Adapter pattern yana da wuce gida sosai, mahimmar pattern don haɗin interfaces marasa daidaituwa (lamuran ɗari, tsohon code, APIs daban-daban) ba tare da canja ko daya — buƙa gaske a kullum — da kuma yana bayar da warware mai mahimmanci, da tun sanin abin da yake yi, amfaninta, da fa'idoinsa yana da dogaro a gaske don haɗin aiki, sanin Adapter pattern yana da mahimmanci, sanin yadda aka tsara da ake buƙata a gaske — pattern da ake buƙata sau da yawa don aikin gaike na haɗin code marasa daidaituwa, bayar da haɗi da warware, da mahimman ilimin yadda aka tsara don buƙa gaske, a mai kumfa na sayar da sassa daban-daban na code su aiki tare.