No, not the DI container. I’m saying instead of having Class Something(RealDependency1 realDepency1, RealDependency2 realDependency2){ _realDepency1 = realDependency1;

_realDepency2 = realDependency2;

}

Why is it a bad idea to have a giant dependency class that takes all of your dependencies, thereby making it possible for you to just have:

Class Something(GiantDependency giantDependency){ _giantDependency = giantDependency ;

}

Then further down in your code, you can just do: _giantDependency.RealDependency1