Skip to content

Streamlined exceptions thrown

Compare
Choose a tag to compare
@hsehszroc hsehszroc released this 21 Jun 10:14

Feature:

  • InvalidPipeline exception now has two new methods:
    • InvalidPipeline::getSubject() -> Gets the subject that was being processed by the pipe throwing the exception. Thus, it will return the immediate previous version of the subject.
    • InvalidPipeline::hasSubject() -> Determines whether subject has been added to exception or not.

Enhancement:

  • Streamlined exceptions thrown by the Pipeline. It can now either be:
    • InvalidPipe -> Application level error where given Pipe is not a valid Pipe variant, or
    • InvalidPipeline -> Any other variant will be transformed to this exception.
  • When exception catching function/closure is provided to Pipeline::sealWith() method, it will not catch InvalidPipe exception anymore. This is an application level error and MUST BE FIXED.
  • App Container no longer verifies before resolving the classname. It is suitable in situation where the given classname has no dependencies and no Auto-Wiring is necessary.