See on Scoop.itAngular.org.il

It used to be that my natural inclination would be to wire my view templates in a manner that made assumptions about the users’ intentions and expectations, based on my understanding of the requirements. This could be seen not only in the way that I named the properties and methods that would be exposed by the controller / view model, but in the way that the view interacted with these properties and methods. Take the following AngularJS view template code as an example:

See on ify.io

Posted in: Articles.
Last Modified: March 22, 2014

Leave a Reply