PSR-11 (ContainerInterface) about container HOT 7 CLOSED

@XedinUnknown very good catch, and I'm not sure how this works either, it must fallback from the alias if there isn't a clash. Will test that out later to see if it's the case

from container.

This requires no action in regard to container interop as a composer update will bring in the change. However there will be a breaking change update to depend directly on PSR-11 some time in the near future.

from container.

@philipobenito correct me if I'm wrong but... you can just add a implements PsrContainerInterface, no? It's just a new minor version. Look at this PR to Symfony to see what I mean:

symfony/symfony#21265

Cheers

from container.

@hannesvdvreken Correct but I have some other BC changes planned so makes sense to all come together and remove the middleman dependency.

from container.

Ah, I see. Didn't know stuff was about to change.

But are you open for small incremental steps to allow PSR-11 now? Instead of holding it off until rewrite is ready?

Seen #123? just asking.

from container.

Just Looking :-)

from container.

The temporary interface Interop/Container/ContainerInterface extends the PSR-11 interface, so anything that allows the temp interface allows the standard, as well, and this doesn't seem to be a problem.

What does seem to be a problem, however, is League\Container\Container, or more precisely its definition. It says that the container implements some ContainerInterface, but this name is not imported. There does not appear to be a League\Container\ContainerInterface, and the interop container is aliased to InteropContainerInterface, so I'm not sure how this code works.

from container.