title: Repeating module name for each module component
body: <p>The famous <a href="https://docs.google.com/document/d/1XXMvReO8-Awi1EZXAXS4PzDzdNvV6pGcuaF4Q9821Es/pub">Best Practice Recommendations for Angular App Structure</a> blog post outlines the new recommended angularjs project structure which is now component-oriented, not functionally-oriented, or as named in the <a href="https://github.com/yeoman/generator-angular/issues/109">initial github issue</a> - "Organized by Feature".</p>
  
  <p>The blogpost suggests that each file inside each module should start with the module name, e.g.:</p>
  
  <pre><code>userlogin/
      userlogin.js
      userlogin.css                
      userlogin.html                
      userlogin-directive.js
      userlogin-directive_test.js
      userlogin-service.js
      userlogin-service_test.js 
  </code></pre>
  
  <p>The question is: what is the point, pros and cons of repeating the module name inside each filename in the module as opposed to having the files named functionally? For example:</p>
  
  <pre><code>userlogin/
      userlogin.js
      userlogin.css                
      userlogin.html   
      controllers.js             
      directives.js
      services.js
  </code></pre>
  
  <hr>
  
  <p>The reason I ask is that I'm coming from a <a href="https://www.djangoproject.com/"><code>Django</code></a> world where there is a somewhat similar idea of having <a href="https://docs.djangoproject.com/en/dev/ref/applications/">projects and apps</a>. Each app usually has it's own <code>models.py</code>, <code>views.py</code>, <code>urls.py</code>, <code>tests.py</code>. There is no repeating app name inside the script names.</p>
  
  <p>I hope I'm not crossing an opinion-based line and there is a legitimate reason for following the approach.</p>