Code Organization in Large AngularJS and JavaScript Applications

Re:Code Organization in Large AngularJS and JavaScript Appli... by tinco on Tuesday April 23, 2013 @02:46PM (#5597132)

I'm building a rails+angular app at the moment, and sort of fell by default in the component-type folders. Reading this blog makes me think that you're right and topical folders are much better, but then an alarm bell goes off. If this is a good way of doing it, why isn't it the Rails way of doing it?

Does anyone know if the Rails core team ever discussed using this directory layout? I know that it would take a fairly big rewrite of some glue logic in Rails that we all know and love, but merely 'hard to do' often does not stand in the way of 'the right way' in Rails.. right?

Can anyone point out something that immediately stands out as possibly problematic?

[ Parent | on HN ]

Re:Code Organization in Large AngularJS and JavaScript Appli... by stackus on Tuesday April 23, 2013 @04:15PM (#5597660)

I thought the same thing.

In my minds eye I don't see a nice place to stuff views. Module specific ones could live inside the module but Rails has layouts and also typically has shared views.

Sinatra would be a good framework to play around with this structure.

[ Parent | on HN ]