3 ms·
While I love Angular, I feel the author is wrong on a few things. It doesn't provide a way to structure your codebase, that's still up to you… directives.js isn
by snikch 13y ago
While I love Angular, I feel the author is wrong on a few things. It doesn't provide a way to structure your codebase, that's still up to you… directives.js isn't going to scale at all. That's also one of the things I love about angular. The code is modularised, but that isn't enforced on the filesystem. You can choose to lump things into files in a folder for directives, or you can put all your routes, directives, filters etc for each feature in a feature folder. You have plenty of control.
Also, I feel like their example is better served as a filter, rather than a directive.
- xonecasacenox 13y agoI agree with you that the structure is still up to the developer, but if you get too creative you'll end up in a mess of code. In this thread other organization approaches have been suggested, that are in my opinion better than the angular seed suggestion. The point I try to make is that Angular when compared to other existing options is more structured. How do you find the balance between flexibility and structure depends on your team and project. After you wrote about my example, I realize that you are correct, it was not a great one. My bad!