title: Injecting direct object dependencies, or methods directly as well
body: <p>A best practice in DI I've read in a few places is not to inject object B just to get at object C, but to inject C instead. </p>
  
  <p>But if a single method from C is all that is required, would you just inject that method instead of C?</p>
  
  <p>If so, what about if a few methods from C were required? Is there a point that it's just more convenient to pass in the full object and live with the fact that you're getting stuff you have no interest in?</p>
  
  <p>Or does that point indicate that maybe class C has too many varied responsibilities and needs to be extracted into multiple smaller classes, the objects of which can then be injected without as much baggage?</p>
  
  <p>Don't be afraid to state the obvious, this is all new to me.</p>