> > The second one is a really technical consequence I didn't realize when > writing the previous comment: > > It makes this statements useless (which is a good thing since that's the > one we're worried about): > > > A call to get can trigger additional calls to get (to fetch the > dependencies). If one of those dependencies is missing, the > NotFoundExceptionInterface triggered by the inner get call SHOULD NOT > bubble out. Instead, it should be wrapped in an exception implementing the > ContainerExceptionInterface that does not implement the > NotFoundExceptionInterface. > > If one wants to be able to really differentiate these situations, one can > already do: > > just check "has" before "get". If, after doing so, "get" throws a > NotFoundExceptionInterface, then it's a second level missing dep. Isn't > it? > > This.
This is really what I realized yesterday and what I meant to say in my previous post. Have a look at the PR I wrote: https://github.com/php-fig/fig-standards/pull/869/files That's exactly what you are proposing in your comment (I'm removing the complete statement you are worried about). Are we on the same line here or is there something else you would change? Reading your comments, I believe we have exactly the same idea. ++ 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/d0a09d7a-b629-4a12-a6ed-403c14766430%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
