JavaScript Instances

Share This Post

In the last post, I briefly discussed JS constructors. In that post, I showed how to create an instance of a constructor with the new operator. Our constructor was rather ‘blah’. So let’s see how we can access constructor instance properties and methods.

// Lets create a horse constructor because I like horses...lol
function Horse(name) {
    let speech = 'Neigh';
    this.name = name;
    this.speak = function() {
        return speech;
    }
}

The aforementioned constructor code gives us a horse constructor to be able to create multiple horse instances.

let trigger = new Horse('Trigger');
console.log(trigger.name); // Outputs 'Trigger'
console.log(trigger.speak()); // Outputs 'Neigh'

We can create any number of instances and call the properties and methods of that instance which has been “copied” from the constructor.

We can also use the prototype property built into JS to add new constructor info…

Horse.prototype.munch = function(){
    return 'munching on hay';
}
console.log(trigger.munch()); // Outputs 'munching on hay'

We can also use the object’s defineProperty method to create properties on the fly. The first item it expects is the object upon which to run. In this case, it is the trigger variable. The second thing it expects is the name of the property along with the value of said property…

Object.defineProperty(trigger, 'color', {value:'brown', writeable:true, enumerable:true, configurable:true});
console.log(trigger.color); // Outputs 'brown'

So, as you can see, there are a myriad of ways to create a constructor and even adjust it on the fly, which may be a good or bad thing… 😉 Anyway, I hope this is helpful to you.

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.