An EndDash developer now has a failing spec for interpolating attributes in EndDash
EndDash developers now no longer have weird behavior when using 'trigger' to fire a change event on attribute interpolation
Optimize code that parses a string that represents an elements attribute to the properties on the model that are in that string
EndDash users still would be weirded out that a change event would now not update the DOM, add another failing spec which shows that change:attribute updates the dom, but not change
EndDash users can now fire either 'change' or 'change:name' on a model bound to a DOM attribute in order to force the DOM to update based on model changes
EndDash Developers now see better formatted code which gets the events being listened to by attribute.js
Merge pull request #186 from Amicus/fix-issue-185

Fix issue 185