{"comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/fc5dc0d579fb554752763792a2d5f449?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"fc5dc0d579fb554752763792a2d5f449","url":"https://api.github.com/users/IgorMinar","login":"IgorMinar","id":216296},"position":27,"updated_at":"2011-11-11T22:19:32Z","commit_id":"f6ba5103e8c3bd6747b01a37648ae24a1647756b","url":"https://api.github.com/repos/mhevery/angular.js/comments/712262","line":891,"body":"I'm not sure if this is a terribly useful directive. What I want to see is `ng:app` which is a glorified `ng:module` - there is just one of them, it is used instead of ng:autobind as a marker for root element that hold the root scope and injector.\n\nng:module could be useful for modularization, but in that case, you likely want the info about the required module to be in javascript rather than in the template (so that we don't get into the ng:controller situation again).","html_url":"https://github.com/mhevery/angular.js/commit/f6ba5103e8#commitcomment-712262","id":712262,"path":"src/directives.js","created_at":"2011-11-11T22:19:32Z"}}