title: NestJS with TypeORM: When using custom repository, is a service needed anymore?
body: <p>Newbie question:
  When working with NestJS and TypeORM, and one has created a custom repository (which extends the standard repository), <strong>is a seperate service class needed anymore?</strong></p>
  
  <p>At the moment, I'm working only with the custom Repository class and it works fine, but I'm not sure if this is correct and perhaps has some side effects.</p>
  
  <p>Btw, in another project i have no custom repo, only a service which get's two standard repo's injected, and this works also fine.</p>
  
  <p>Regards,<br>
  sagerobert</p>