Custom exceptions.

Custom exceptions are handy if you want to trap them specifically outside of a generic exception that can be caused by something else. For instance if you have a custom exception of InvalidImageDimensions then you could use it like :

...
try {
    $resizedImage = $this->resizeImage($originalImage, 1024, -768);
} catch (InvalidImageDimensions $e) {
    // do something specific
} catch (Exception $e) {
    // some other thing
}

Maybe you only want to catch your own exceptions and let the others bubble up the system etc. In general I think they're best used sparingly though.

@phpMick Completely up to you, but custom exception classes are a bit easier to diagnose than a generic Exception with a message.

Consider:

throw new \App\Labels\ImageMissingException;

Over:

throw new \Exception('Image is missing.');

Looking at the former in your logs, you’d be able to instantly see what the issue is from the exception class’s name.

Custom exception is good when you want specific way to dealt with that exception. For instance, sometimes you want redirection to home page when you catch exception of that type.

here is link to thread how to handle custom exception

https://laracasts.com/discuss/channels/laravel/how-do-you-handle-your-custom-exceptions-in-laravel-5051

I think I got it.

I will do it like this:

}catch(\LabelPrintingException $            

"Turn the printer on you muppet"

        }catch(\Exception $e){
   
    Log the actual error.
    Nice message to user.
        }

The I can handle them differently, with LabelPrintingException I can pass a message to the user, if any other exception happens, i can just log it.

Mick