Use PSR-11 Container Interface

[geerteltink]

container-interop can't be removed completely... ZendViewRendererFactoryTest has tests for Zend\ServiceManager\AbstractPluginManager, which is not updated yet.

[michaelmoussa]

@xtreamwayz this looks good (so far) but I suggest waiting on merging this until container-interop can be removed completely. The partial changes are already a BC break, and removing container-interop entirely later would be another BC break. Might as well do it all in one shot.

There are quite a number of references to it in zendframework/zend-servicemanager which likely tie in to other ZF components, but as long as it gets a major version bump, we shouldn't need to update the other components right away.

[michaelmoussa]

I went ahead and submitted a PR to both zendframework/zend-servicemanager and zendframework/zend-eventmanager for interop -> PSR-11. Maybe we can end up removing interop from this PR entirely like you were able to do for the other two renderer repositories.

[michalbundyra]

I think it should be marked as BC Break, because we change type of exception. Maybe type hint in factories is not a big issue, don't think so that somebody extends these factories and override __invoke method. But anyway... it's still possible.

[michalbundyra]

We don't need above line. We are not using this library here anymore.
We need of course conflict entry, as it is now below.

[michalbundyra]

Isn't it here BC Break? If somebody catch exception on ContainerException it will stop work.

[weierophinney]

If they were catching Interop\Container\Exception\ContainerException, however, and the container in use implements PSR-11 only, then there's breakage.

[mwillbanks]

At this point this is starting to look really good. I do think we need to support PSR-11 properly, there are some other comments that might be necessary to look at prior. My approval is strictly on the code and the implements.

[weierophinney]

Thanks, @xtreamwayz!