Skip to main content

Backbone.js - Model validation in constructor

I've started to look at various Design Patterns in JavaScript and one of most popular Design Patterns in any language is the MVC Pattern. In JavaScript, there are various libraries out there which helps in modularizing the application. However, I've heard a lot about Backbone.js and I thought this would be the right time to give it a try. I've not learnt Backbone completely, but I've gained a good understanding of the Model part of the MVC in Backbone.

To build a Model, you would extend Backbone.Model and provide instance properties like - defaults, validate, initialize etc,. I assumed that if the validate function is defined, it would be invoked whenever an instance of the Model is created, but this was not true. To overcome this, I tried to call validate method in initialize but this did not suffice the purpose, since this function (initialize) was called after the Model was created. On reading further and on trying out some options I understood that the validate function is called whenever a user tries to set a property on the Model (carObj.set('property',value)):

As seen in the above code snippet, an instance of Car is created even though the 'color' attribute is not specified. Here's the console output:

Inside initialize
d {attributes: Object, _escapedAttributes: Object, cid: "c0", changed: Object, _silent: Object…}
_callbacks: Object
_escapedAttributes: Object
_pending: Object
_previousAttributes: Object
_silent: Object
attributes: Object
brand: "Ford"
model: "Figo"
__proto__: Object
changed: Object
cid: "c0"
__proto__: x 
Is Model valid: false 
Error Occurred 

Although you can call isValid function on the object (carObj.isValid()) and validate the Model once it has been created, but I wanted the Model to validate the data before returning an instance of it. I added a constructor property to the object and was able to validate the data there:

As you can see, I'm overriding the constructor function. Here I'm calling the validate method in constructor and checking whether the data is valid, if any of the required arguments are not present then the validate method would return a string 'Error Occurred'. The constructor would then return an empty object.

It is important to note that since we are overriding the constructor property and providing our own implementation, we need to call the parent constructor (Backbone.Model) explicitly to initialize the Model, this would then construct the object and invoke the initialize method.


Popular posts from this blog

Adding beforeRender and afterRender functions to a Backbone View

I was working on a Backbone application that updated the DOM when a response was received from the server. In a Backbone View, the initialize method would perform some operations and then call the render method to update the view. This worked fine, however there was scenario where in I wanted to perform some tasks before and after rendering the view. This can be considered as firing an event before and after the function had completed its execution. I found a very simple way to do this with Underscore's wrap method.

On GraphQL and building an application using React Apollo

When I visualize building an application, I would think of using React and Redux on the front-end which talks to a set of RESTful services built with Node and Hapi (or Express). However, over a period of time, I've realized that this approach does not scale well when you add new features to the front-end. For example, consider a page that displays user information along with courses that a user has enrolled in. At a later point, you decide to add a section that displays popular book titles that one can view and purchase. If every entity is considered as a microservice then to get data from three different microservices would require three http  requests to be sent by the front-end app. The performance of the app would degrade with the increase in the number of http requests. I read about GraphQL and knew that it is an ideal way of building an app and I need not look forward to anything else. The GraphQL layer can be viewed as a facade which sits on top of your RESTful services o

De-obfuscating javascript code in Chrome Developer Tools

I had blogged about JavaScript debugging with Chrome Developer Tools  some time back, wherein I have explained how these developer tools can help in debugging javascript code. Today Google Chrome 12 was released and my Chrome browser was updated to this version. As with every release, there have been some improvements made on performance, usability etc,. One feature that stood out for me is the ability to De-obfuscate the javascript code. What is Minification? Minification is the process of removing unnecessary characters such as white spaces, comments, new lines from the source code. These otherwise would be added to make the code more readable. Minifying the source code helps in reducing the file size and thereby reducing the time taken to download the file. This is the reason why most of the popular javascript libraries such as jQuery are minified. A minified jQuery file is of 31 KB in size where as an uncompressed one is about 229 KB. Unfortunately, debugging minified javascript f