Exceptions in Laravel: Why/How to Use and Create Your Own 

Hi there. Can you explain more about that, or is there any references that I can read on? Thanks.

Please explain, Intresting point of view

I agree with you

I think the idea here is that you can have the same standard exception meaning different things and needing different treatments in different places. Here it was good to take a general ModelNotFoundException and instead throw a UserNotFoundException, so that you can handle it in a different way. Basically, ModelNotFoundException can be a lot of different stuff, and for each one of them you may want to report or render different things. I think this is why you catch and throw in controllers/services in this case, so that you may specify and treat them accordingly.

That would not be one video, it would be a series of videos on different topics :)

Good point, no need for try catch then, forgot to mention it in the video.

laravel.com/docs/8.x/errors#renderable-exceptions public function render($request) { $error=$this->getMessage(); return view(' 'someview ', ['error'=>$error] ); }

nice)

Some of the things are happening during the editing of the video, maybe it was a cut to make the video shorter. I don't have anything specific set up in my phpstorm, it's the defaults.

​@@LaravelDaily it doesn't seem to me that there are any cuts in this place. Let me please rephrase this question and make it less vague. And I need to clarify that by highlight I mean to select. What combination of keys have you pressed to get PHPStorm automatically select the whole method call on the `$exception` variable? The code was: dd($exception->getMessage()). You made a decision to wrap the variable with the get_class() function. You typed get_class() before the `$exception` variable, then you deleted the closing `get_class` parenthesis, and then you pressed something and the whole `->getMessage()` on the $exception variable became selected. And then you deleted this selection with one key, as we usual do. It happens at 5:46 - 5:47. I've tried to do the same step by step, using different keys which I know, but without any result. UP: I rewatched that moment several times and it seems that it was a cut after all. But this possibility to change a code that way looks so cool to me that I obviously need to think about how to realize such a functionality, through macros or something similar :) Anyways, thank you very much for your answer.

That's actually my style of explaining the topics - to talk about how to use stuff practically, and not how it works under the hood. If you do want to find out about Laravel internal Handler and how it works, I won't explain it better than this page: laravel.com/docs/8.x/errors What exactly is not clear on how to use it? To me, it is explained in a few examples on that page.

@@PovilasKorop Thanks for your answer... First, it's not clear how to properly catch fatal errors in app/Exceptions/Handler.php, and, for example, send email notification with fatal error description... Second a little confusing thing, is your phrase that handling exceptions improves code readability... No doubt it's right, but on recent job interview, while talking about exceptions, they mainly asked how to handle different types of errors, on which types of errors does script stops, and other error related questions. Unfortunately, they didn't explain why are they asking about that. So now I’m going to suspect that main purpose of "Errors & Logging" Laravel documentation chapter and of using exceptions, is not just improving code readability, but something more...

@@inf2004 well the whole topic is indeed much deeper, and it's not even about Laravel, it starts with PHP errors and exceptions (and these are different), also types of errors (error, warning, notice etc) and only then php exceptions, and only then Laravel logic on top. So I agree I could talk much deeper on that, but my goal on this channel is to give the most practical lessons in short videos, and not hours of lectures about theory. For that, there's always documentation, books, courses and longer tutorials.

@@PovilasKorop Understood. Thanks for your answer and excellent videos.

i have same question.. anyone?

No, totally not, should be a general NotFoundException with probably a different message, or different action in "catch" section of try-catch.

It's not better or worse, it depends on what is your goal. For Vue, it plays not with exception classes, but with status codes like 404.

You don't. Route model binding throws ModelNotFoundException automatically.

PhpStorm.

@@PovilasKorop thanks for both the name and the tutorial.. Very helpful, I'm one of the culprits that just dumps try catch without understanding whats happening.lol

I'm not saying you should use try-catch everywhere - only when it's actually clear that some kind of exception may appear, and you know/expect it.

@@PovilasKorop Wau. Thank you so much. And for your videos too. There are great...

Nevermind - I see it. I was going to just delete this but maybe someone else gets the same question some day and it helps them. The answer is that the $exception variable is created on the line above (line 16), then used in the next line (line 17).

Thanks for the tip, this is the way I can see someone actually WATCHING my videos :) P.S. On my old Macbook 2015, which I use for shooting videos, the Down Arrow is almost not working, so I'm trying to avoid it :)