AngularJS Style Guide

I still don&#x27;t understand why everyone recommends different folders at the project root for controllers, directives, services, etc... You end up with closely related code being far apart. It&#x27;s a thoughtless way of dividing up your files based on the most obvious feature rather than how things actually fit together.<p>My idea of a good modular file structure is that you could delete any random directory and delete it and it would lop off that feature as cleanly as possible. Each directory should represent an angular module, and each module should contain the routing, controllers, services, directives, and tests that it uses. If some of these are used across the app then you can have a &quot;common&quot; module.

I&#x27;m coming back to JS development after several years away and my first impressions of Angular are that it seems very complicated and over-engineered, with a lot of fairly abstract concepts to digest to get even simple things working. React.js seems so much simpler but there does seem to be a lot of community support for Angular.<p>Should I invest the time and learn Angular or go with React instead? Web components seem likely to change the whole web development landscape but my impression is that they&#x27;re not quite ready for prime time yet.

Very helpful. I&#x27;ve unsuccessfully search for a way to do one-time binding before in a data intensive application and never came across the {{::ctrl.foobar}} syntax.<p>One thing I&#x27;m hesitant about is their advice to use directives instead of ng-controller=&quot;MyCtrl&quot;. Since controllers really are app specific glue code I rarely find myself wanting to reuse them - what advantages are directives supposed to give here?

Anyone have experience one way or the other with the pattern of including test files with the features as opposed to under an alternate directory structure? I usually put tests and application code in parallel directories so that the tests are all in one place, but curious if anyone has seen big advantages one way or the other

Todd Motto&#x27;s angular style guide [1] has been one of the most helpful to me. It&#x27;s always good to read multiple style guides and cherry-pick what works best for you :)<p>[1]: <a href="https://github.com/toddmotto/angularjs-styleguide" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;toddmotto&#x2F;angularjs-styleguide</a>

I find myself counter to the popular opinion on the use of controllerAs for mostly semantic reasons (IMO, a controller orchestrates services, $scope included, rather than containing data or references to data), though there are obvious and not-so-obvious tradeoffs with either choice.<p>That said, this style guide definitely has the strongest (almost convincing) argument I&#x27;ve seen for using controllerAs and does not have the inconsistencies I&#x27;ve found in other guides (`this` is not bound to `$scope` as a couple popular guides claim). Good stuff.

Meh. NgAnnotate is way better than duplicating code. Be DRY, not pedantic.

A minor nit, the TL;DR is just an outline. I was hoping for a simple statement of the problem with a conclusion and the rest of the article would present the details, more of a real overview or synopsis.

I got a lot out of this. I’ve never worked in a platform that evolves as rapidly as Angular, and have found myself blinded by “last year’s advice” a few times. Quite a bit of modern thinking here.

logically this should come from Google (the author of AngularJS)... anyway, thanks, I&#x27;ll definitely try to use it

Is this article an ad?

The actual post title is: &quot;The GoCardless AngularJS Style Guide&quot;. I was expecting something about how they needed to do XYZ to make Angular <i>run</i> well rather than how they scale up <i>development</i>.