Details

    • Type: Language-Specification
    • Status: Active
    • Resolution: Unresolved
    • Labels:
    • Message:
      Change this type to be a class deriving from "Throwable".
    • Highlighting:
      • Primary: The caught class name
      • Secondary: The name of the class in its class definition.
        • message: 'Class definition.'
    • Impact:
      Unknown 'null' severity
    • Likelihood:
      Unknown 'null' severity

      Description

      Instances of classes that do not derive from the "Throwable" interface cannot be used in a PHP "throw" statement. Thus, it does not make sense to try to catch such objects within a "try-catch" block.

      Many built-in exceptions such as "Exception" and the SPL exception classes do implement the "Throwable" interface and can be extended when creating custom exceptions.

      This rule raises an issue when the classes used to specify the type of objects to be caught in a "try-catch" block do not derive from "Throwable" .

      Noncompliant Code Example

      class NoThrowable {}
      
      try {
          foo();
      } catch (NoThrowable $e) { // Noncompliant
      }
      

      Compliant Solution

      <?php
      
      class SomeThrowable implements Throwable {
          // Implementation of the Throwable methods
      }
      
      try {
          foo();
      } catch (SomeThrowable $e) { // Compliant
      }
      
      class SomeCustomException extends Exception {}
      
      try {
          foo();
      } catch (SomeCustomException $e) { // Compliant
      }

       

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            karim.ouerghemmi Karim El Ouerghemmi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: