René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Should client/app/admin and account be full components?","articleBody":" - [x] I understand that GitHub issues are not for tech support, but for questions specific to this generator, bug reports, and feature requests.\r\n\r\nItem | Version\r\n----- | -----\r\ngenerator-angular-fullstack | 4.1.2\r\nNode | 6.9.4\r\nnpm | 4.1.2\r\nOperating System | OS X 10\r\n\r\n\r\nItem | Answer\r\n----- | -----\r\nTranspiler | Babel\r\nMarkup | Pug\r\nCSS | SCSS\r\nRouter | ui-router\r\nClient Tests | Mocha\r\nDB | Sequelize 4.0.0-2 / PostgreSQL 9.6.1\r\nAuth | Y\r\n\r\n[account(auth)](https://github.com/angular-fullstack/generator-angular-fullstack/tree/master/templates/app/client/app/account(auth)) and [admin(auth)](https://github.com/angular-fullstack/generator-angular-fullstack/tree/master/templates/app/client/app/admin(auth)) are implemented as loosely coupled controllers. Their implementation differs from the generated **main** component (which is an AngularJS component). Also, possibly change their controllerAs to $ctrl from vm.\r\n\r\nWhat are your thoughts about making admin, login, settings, and signup into full AngularJS components? This would improve consistency as well as lay the foundation for those moving to 2.0.","author":{"url":"https://github.com/nstuyvesant","@type":"Person","name":"nstuyvesant"},"datePublished":"2017-02-04T18:37:30.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/2490/generator-angular-fullstack/issues/2490"}