title: Is injecting repository in aggregate root / entity considered bad design?
body: <p>I am trying to learn about details of domain driven design and i came to this question.
  I found many examples with:</p>
  
  <ol>
  <li>Defining repository interface within the domain</li>
  <li>Defining repository implementation somewhere else</li>
  <li>Inject repository interface into aggregate root</li>
  </ol>
  
  <p>On the other hand, there are examples that strictly go against it and do all repository related stuff from service.</p>
  
  <p>I cannot find authoritive answer and explanation: is it considered a bad practice and if so - why?</p>