Add a shortcut assertion for parametered classes of services about symfonydependencyinjectiontest HOT 3 CLOSED

Thanks for submitting this issue. However, I don't think this is a good use case: if you know that a service definition should have a parameter as its class, you should assert exactly that.
Besides, writing unit tests for a container extension is about verifying that its load() method does what it should do (e.g. load some services, set some parameters, modify existing ones, etc.). Validating the eventual consistency of the service definitions in the end should be done by a functional test (or by https://github.com/matthiasnoback/symfony-service-definition-validator).
Using parameters for service classes is something the framework itself does most of the time. I don't really encourage it. It clutters the dumped container with many parameters that are never used at runtime. Parameters should only be used for classes when they are likely to be changed by some other bundle. Then that bundle does not need to call getDefinition(...)->setClass(...) but instead can simply change the value of the parameter.

from symfonydependencyinjectiontest.

Thanks for your point of view. If parameter for classes should be used or not may not be my intention for a topic of this issue.
Anyhow, if anybody likes the shortcut, they can copy it from my first post.

How about waiting for other opinions about such a shortcut?

from symfonydependencyinjectiontest.

Alright, though I'll close this issue for now, in order to clear my view on pending issues. Thanks again!

from symfonydependencyinjectiontest.