theironcook/Backbone.ModelBinder — pull request #102 by zveroboyisme (2012-12-03 22:01:53+00:00)
Title: Setting the class even when previous value is undefined

I came a across an issue where an attribute on the model was originally undefined at the time of binding, and converter function returned a, let's say, default class to be added to the dom element. However, when the attribute was set (i.e. no longer undefined), because the previous value was undefined, the originally added class was not removed, since the previous value is check for being defined. So, I think it is worth checking for a such condition by testing the current value of the attribute. If the current value is defined then (regardless of whether or not previous value was defined) go ahead and call converter function and, consequently, remove the returned class from the dom element. Please, consider this change, and don't hesitate to contact me for any further discussion. Thank you.