Prefer composition over inheritance

As the rule from title tells us, we should favor composition when we code. So maybe it’s worth to replace all examples using class with proper ones based on composition?

Let’s take the “Avoid conditionals” section for instance. It shows the example of inheritance while the goal was to encourage the developer to use composition. Below you can see how the definition of different airplanes could look like (using composition):

const Airplane = {
  getName() {
    return `${this.name}`
  }
}

const AirbusA380 = { 
  name: 'Airbus A380',
  getName() {
    return  `${Airplane.getName.call(this)} of ${this.airline}`
  }
}

const Cessna = { 
  name: 'Cessna'
}


// define factory functions (airbusA380, cessna)
const airbusA380 = (state) => Object.assign(
  {},
  Airplane,
  AirbusA380,
  state
)

const cessna = (state) => Object.assign(
  {},
  Airplane,
  Cessna,
  state
)

// create instances of airplanes
const emiratesAirbus = airbusA380({
  airline: 'Emirates'
})

const privateCessnaJet = cessna()

console.log(emiratesAirbus.getName()) // prints "Airbus A380 of Emirates"
console.log(privateCessnaJet.getName()) // prints "Cessna"

What do you think about replacing all class examples with composition-based ones?

[ericelliott]

👍

[jokeyrhyme]

Eric Elliott sold you blue water and called it medicine.

@Jeff-Mott-OR let’s try to keep things civil and respectful. You can discuss the merits or pitfalls of an idea without maligning the character of someone else.

It’s obvious that you are passionate about this discussion, let’s just try to be passionate and constructive.