I am never a big fan of using constructor injection, even though it's really convenient in many cases.
Personally, I lean to have property injection or a wrapper injection; however, that doesn't mean I am against using constructor injection. You just need to be careful.
The bottom line is, if you have too many parameters in whatever (either constructor or a public method), it's going to reduce the readability.
If an object requires a lot of input to become useful, it is possibly this object has too many responsibilities, or it could become a base abstract object, or it could benefit from a wrapper, or it could rely on a dedicated factory, and so on...
For myself, if I have more than 10 parameters in the constructor, I will think twice of adding more and try to refactor the object. But just my 2 cents
Personally, I lean to have property injection or a wrapper injection; however, that doesn't mean I am against using constructor injection. You just need to be careful.
The bottom line is, if you have too many parameters in whatever (either constructor or a public method), it's going to reduce the readability.
If an object requires a lot of input to become useful, it is possibly this object has too many responsibilities, or it could become a base abstract object, or it could benefit from a wrapper, or it could rely on a dedicated factory, and so on...
For myself, if I have more than 10 parameters in the constructor, I will think twice of adding more and try to refactor the object. But just my 2 cents