AngularJS Cheat Sheet [pdf]
dncmagazine.blob.core.windows.net
AngularJS Cheat Sheet [pdf]
1–10 of 48 posts
Re: AngularJS Cheat Sheet [pdf]
#2Nice domain name.
Re: AngularJS Cheat Sheet [pdf]
#3Thanks for posting this. Really looking forward to trying out some of the unit testing advice!
Re: AngularJS Cheat Sheet [pdf]
#4I love cheat sheets! I actually consider them the best way to learn a framework. This one's excellent. Wish I could find one as good for Meteor.
Re: AngularJS Cheat Sheet [pdf]
#5Nice domain name.
In my opinion this is hosted on Azure and all azure containers have the same domain name (for obvious reasons).
Nice cheat sheet though!
Re: AngularJS Cheat Sheet [pdf]
#614 pages for a cheatsheet!
The ones for emacs/vim are 1 page only, I guess we have a measure of the complication of angular now.
Re: AngularJS Cheat Sheet [pdf]
#714 pages for a cheatsheet! The ones for emacs/vim are 1 page only, I guess we have a measure of the complication of angular now.
That's what I thought. At which point do they stop being cheat sheets and start been books?
Re: AngularJS Cheat Sheet [pdf]
#814 pages for a cheatsheet! The ones for emacs/vim are 1 page only, I guess we have a measure of the complication of angular now.
I wouldn't call this a cheatsheet in the same sense of the emacs/vims ones which list mostly keyboard mapping shortcuts. This is more of an abbreviated overview of the framework, complete with sample code demonstrating the patterns.
Re: AngularJS Cheat Sheet [pdf]
#9This looks like a good resource. But number 28 is wrong:
> Always have a ‘.’ in your ng-models which insures prototypal inheritance.
That isn't what that does. The egghead.io Angular videos also get this wrong. I really think that the vast majority of Angular programmers don't really understand how its scoping works. I've ranted about this before [1], it's just ridiculously complex.
Some scopes inherit prototypically from their parents, and others don't, and you can't tell or affect it from the markup. The dot just means you're referring to a property of an object on the scope. If the object is somewhere in the scope inheritance chain, two directives attached at different points in that chain can share data by pointing to the object. If the object isn't there, what the name points to is actually non-deterministic. Ng-model silently creates it, and the point in the chain at which it creates it depends on which directive wanted to write to the property, which might depend on the order in which the user interacts with the different elements on the page.
[1]: http://larseidnes.com/2014/11/05/angularjs-the-bad-parts/
Re: AngularJS Cheat Sheet [pdf]
#10I love working with angular, but the intense competition from other technologies combined with the overall negativity towards it has turned me off. The long term future of angular seems very uncertain.