When you define a service in your configuration, which is created by a factory, the plugin seem to check against arguments of the class-constructor and not the factory-method, which is used. This cause false warnings and proposals. This also happens, when extending services (parent-property).
I have this issue in a yaml-configuration file. I did not test it in other configuration formats.
Oh my gosh, just found another case, here an example of the configuration part, in which I get a "missing service":
calls:
- method: "initFilters"
arguments:
-
- "@resource.product.search_filter"
- "@resource.product.date_filter"
When you define a service in your configuration, which is created by a factory, the plugin seem to check against arguments of the class-constructor and not the factory-method, which is used. This cause false warnings and proposals. This also happens, when extending services (parent-property).
I have this issue in a yaml-configuration file. I did not test it in other configuration formats.
Oh my gosh, just found another case, here an example of the configuration part, in which I get a "missing service":