Inheritance

Share This Post

In OO languages, we want to stay DRY and avoid getting WET. Inheritance allows us to avoid writing duplicate code. JavaScript classes give us this ability…

class Animal {
    constructor(name){
        this.name = name;
    }     speak(){
        return ${this.name} says “ugh!”;
    }
}  

We can use this animal class and extend (inherit) it to another object. Here’s an example…

class Primate extends Animal {} 
let gorilla = new Primate(‘Bongo’);
console.log(gorilla.name); 

The output would be “Bongo”. We extended the Animal class. This gives us access to all of the functionality within the Animal class. That is how we were able to get access to the name property. Notice that there is no constructor in the Primate class. What if we had one though?

class Primate extends Animal {
    constructor(){}
} 

It would return a reference error because the code is looking to the constructor within the Primate class and not the Animal class. We need it to look to the constructor in the Animal class first. We do this by using the “super” method…

class Primate extends Animal {
    constructor(){
        super();
    }
} 

Our code would still return a reference error because the property value we sent is not going all the way through to the Animal class constructor. We have to send the argument through the super function.

class Primate extends Animal {
    constructor(name){
        super(name);
    }
} 

What if we had a method with the same name in both the Primate class and the Animal class? The secondary class method runs, but if we want the Animal method to run, we use super again…

class Animal {
    constructor(name){
        this.name = name;
    }
    speak(){
        return ${this.name} says;
    } }
class Primate extends Animal {
    constructor(name){
        super(name);
    }
    speak(){
        return super.speak() + “ugh!”;
    } }
let gorilla = new Primate(‘Bongo’);
console.log(gorilla.speak()); 

The output would read, “Bongo says “ugh!”. So we can use inheritance to mix and match functionality and even override if we wish.

Happy Coding!

Clay Hess

More To Explore

Code

Demystifying Scrum User Stories Confirmation: Ensuring Quality and Collaboration

One of the key elements of Scrum is the use of user stories to define the requirements of a system or feature from the perspective of the end user. As teams work through the product backlog, it becomes crucial to confirm the user stories to ensure they meet the desired criteria and are ready for development. In this blog post, we’ll explore the concept of Scrum user stories confirmation and its significance in delivering high-quality products.

Code

The Power of Conversations in Scrum User Stories

At the heart of Scrum lies the concept of user stories, which serve as a means of capturing requirements from the perspective of end-users. However, the true power of user stories lies not just in their written form but also in the conversations that take place around them. In this blog post, we will explore the significance of conversations in Scrum user stories and how they contribute to the success of Agile projects.

Do You Want To Boost Your Business?

drop us a line and keep in touch

Scroll to Top
small_c_popup.png

Need help?

Let's have a chat...


Login

Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 

Register

Begin Your Learning Journey Today!

Come back inside to continue your learning journey.