backbone.validation | validation plugin for Backbone.js | Validation library

Looks like all the views are attached to $content. Whenever you create a new view to this element, a new set of event listeners would be attached to this element.

Ideally you should remove existing views before creating new ones to free up memory using view's remove method.

If you can't do this for some reason and want to keep all view objects created in memory at the same time, they need to have their own elements to bind events to.

You can do this by removing el: $content, This let's backbone create an element for each view.

Then do $content.append(view.el) after the view creation. You'll have to detach these element from $content while creating new views.

Well after dozens of hours trying to fix this, it turns out the error was down to the case of the 's' in my JavaScript module folder.

In ns.package.json I had:

To validate only certain fields, Backbone.Validation offers a modified version of isValid.

If you pass the name of an attribute or an array of names, you can check whether or not the attributes are valid:

Problem solved

So in a plugin documentation is information about validation on model without binding with a view.

Using model validation

The philosophy behind this way of using the plugin, is to give you an easy way to implement validation across all your models without the need to bind to a view. Of course, if you use this option the callbacks to update the view is not executed, since there is no way of knowing what view a model belongs to.

Validation mix-in

To add validation to your models, mix in the validation on the Model's prototype.