> > > PSR-11, aka ContainerInterface, has been sleeping for too long. Let's get > that PSR moving! > > Yeah! Let's do this!
Here is some data from Packanalyst to think on more concrete data: http://packanalyst.com/class?q=Interop%5CContainer%5CException%5CContainerException The "Type hierarchy" section contains all the implemented exceptions. As you can see, there are plenty of classes implementing this exception. At the very bottom of the page, there is the "Interface usage" section (that refers to all the files that are actually "using" this exception. There are 15 files only (and most of them are false positive... I need to work on this feature yet). On a personal note, I have implemented this exception many times (to detect misconfigurations, circular references, etc...), but I have never found a valid use case where I would actually want to catch it. I understand Paul's idea to have a package-specific base exception, but nothing prevents implementing package to have their own base exception. Since this PSR contains only 1 useful exception (NotFoundException), it might not make a lot of sense to keep an additional "base exception". So as far as I'm concerned, I see no objections to removing the ContainerException from PSR-11. On a side note, regarding migration from container-interop to PSR-11, we will probably deprecate container-interop in favor of PSR-11 when it's ready. It the PSR-11 Container interface stays the same, it will be "compatible" with container-interop's ContainerInterface. We could therefore publish a version 1.1 of container-interop's ContainerInterface that simply extends PSR-11's ContainerInterface. That would "automagically" migrate all container-interop projects to PSR-11. This is of course assuming that there is no BC breaks between container-interop and PSR-11. ++ David. -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/18959f56-97be-4e41-904b-b29e94584f32%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
