If you need to know whether dependency of a service is missing and you have some special logic behind it... What about DependencyArgumentTypeMismatchException, MissingRequiredArgumentException and tons of others container-is-screwed exceptions? What makes them less important?
(question to Larry) On Thursday, November 3, 2016 at 12:53:13 AM UTC+3, Matthieu Napoli wrote: > > Splitting off the main review thread, quoting Larry: > > > 1) What other exceptions might get($id) throw besides NotFoundException? > > \Exception (because any exception could be thrown when creating services) > => are you suggesting we should document it in the standard? > > > 2) I would much prefer to see a DependencyNotFoundException defined for > that case than leaving that up to individual implementers. Standard > error handling is just as important if not moreso than the happy path. > > Why/when would one want to catch that exception (use case)? This is not a > need we have seen when using container-interop as of now, I'm of course not > against adding new stuff but we should do it for a reason. > > Matthieu > -- 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/08c7dc35-959b-43f5-abac-fddf2e3f4c31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
