3 ms·
> I consider myself to be a reasonably good js developer, but the internals of AngularJS are overwhelmingly non-approachable. Same here. I'm just getting up t
by louthy 13y ago
> I consider myself to be a reasonably good js developer, but the internals of AngularJS are overwhelmingly non-approachable.
Same here. I'm just getting up to speed with Angular. I spent the past weekend developing a web-app to manage our internal test-process. I like it a lot, I managed to create an incredibly complex and interactive web-app in two days.
Well, I say I like it a lot, I like the idea a lot: data driven mark-up, separation of concerns, etc.
However when it goes wrong it's incredibly difficult to step through the Angular code to work out what on earth is the cause of the issue.
It took me several hours of poking around trying to get this tree-view directive to work:
http://ngmodules.org/modules/angular.treeview http://ngmodules.org/modules/angular.treeview
First to try and work out why the directive wasn't being initialised, then why the parameters were coming through with different names of the properties compared to what the original source expected (ngTreeModel rather than treeModel for example). Then, why on the inner elements of the tree the properties coming through were named as expected!
So exasperated I head over to the documentation for directives, and, yeah, horrible... incredibly dry and terse.
I never quite got to the bottom of the issue, and have deferred working it out until I know Angular a bit more (var treeId = attrs.ngTreeId || attrs.treeId).
But I can't deny that this thing is incredibly powerful, so I think it's worth persevering with. But yeah, some better docs and up-to-date examples would be very, very welcome.
EDIT:
I remember reading this a few months back. Now I get it...
http://www.bennadel.com/blog/2439-My-Experience-With-AngularJS-The-Super-heroic-JavaScript-MVW-Framework.htm http://www.bennadel.com/blog/2439-My-Experience-With-Angular...