Laravel Service Error: Abort or Throw Exceptions? 

Another good way will be to use the Exception Handler, so that your controller is free of try-catch blocks. Great video as always 👍

Exceptions are ignored a lot by devs even tho they can be very helpful with tracking the issues, and you can even send an email to devs when a specific exception occurs. Thanks for the video!!

You're my real teacher and my hero dear. I really love your videos and the way you teach. Wish you luck forever

I use exceptions then catch them using Laravel’s Error Handing features. It reduced the amount of try/catch blocks. For example if an exception extends an MyApiException then I can choose to always return json, but if it extends MyImageConversionException I may throw an error back to the UI. Another use case is to let exceptions bubble up while in development but only log while in production and provide a generic error like “whoops something went wrong” to the user. If you abort you loose the option to control how errors are handled, and you may have to go back and add exceptions anyways.

I think that is a great idea to shoot videos about comments from Laravel Daily. 👍

Laravel has a neat feature with render functions in custom exceptions. So you are able to throw speaking erros for your API e.g. JSON API conform errors, which are pretty nice. In cli you would still have your call stack and the exception message. Try to avoid try catch blocks in your controllers. Btw a dedicated exceptions with disabled debug (which always should be in production) might be bad for FE devs. They wont see the exception message. Please try to work with granulated exceptions. Generalised catching exceptions/throwables might end in unexpected behaviour. You also can watch fur custom eXceptions in your tests.

Nice video ty short and simple

Thank you!

While watching your video, just realized that Laravel Validation won't throw any exception. And that made me thinking: why not make a course/series of how Laravel works internally? I mean... inspecting Laravel's source code

I always structure that way. I throw exceptions and the controller is responsible for sending the appropriate message.

It's better to throw a dedicated exception, then use the Exception Handler or renderable exceptions.

Thanks for the video! How can I catch Exception thrown in StoreUserRequest class failedValidation method?

In order not to turn the entire project into hell with try catch, I use the render method in the exceptions themselves

Doesn't abort and throw exceptions do the same thing?

If you do multiple service actions inside the controller. Should there be one try catch or separate try catches for each sevice action call individualy? So trying multiple stuff and then catch or all separate try catches.

Thanks.

I usually throw exceptions. laravel api route automatically return appropriate json with correct response code

422 vs 400