|
|
|
|
|
|
by istorical
4134 days ago
|
|
|
Don't blame you if you don't have time nor motivation to respond, but care to share a 2 min. description of those rules? I'm a fairly new developer working in my first post-uni role and we're starting to rack up a lot of Angular code and I'm not sure if I'm structuring things right as far as events vs $watches etc. |
|
|
* Use ui-router. Build your app with nested views.
* Any duplicate page elements should be directives. Use isolated scope when you can and pass state into directives explicitly
* Keep model state in services. Controllers handle binding data to $scope (one way, from model to view) and handling events from the view