I have been programming for 30 years and got throw onto a PHP project with no prior experience in the language. These are probably the best programming tutorials I have seen. Very fast paced and all the right information.
Honestly by making this course everyone who is gonna watch it will make it to the pro. There are many many courses for money but all they explain is just basic knowledge and 4 fundamental concepts of OOP. I have never known about autoloading for example and so much more. Thank you GIO. May GOD BLESS YOU.
All instructors who present courses on Udemy and Coursera ...... ,should learn from you how to explain all the things and details( not just the basic stuff) in a simple and accurate way.
Another phenomenal lesson from Gio. The only thing I was having trouble with is that EVERY time I was creating a custom exception class I would somehow forget to put in the App\Exception namespace. The IDE would just chill not warning me about it but the code wouldn't compile even when I manually added the namespace path. So the only solution was to delete and create same class but this time adding the namespace in the creation form itself.
Gio is the ultimate argument against the bearded ones who criticize the use of tutorials for learning. I'm waiting for the Laravel tutorial as a Christmas present.
Bro, this is the best and detail explanation on PHP exceptions. Now i know i could throw my own custom exceptions for database access errors. Only thing is my old complain - too fast. But its ok, i repeat the portion in slow speed.
Great lesson. First exposure to this kind of error handling. I certainly need to explore it more... later. I need to move on, want to get to the end of section 2. Thanks a lot Gio
Really great lesson! Does it make sense to include a "MyAppException"-trait that e. g. includes logging of Exceptions, Handling-Options like communicate to the user, closing the app, returning to last input page and so on and then use this trait in all self-made Exceptions? In addition I would have an interface that contracts the usage of various instructions that clarify which options from the trait or from php built in methods shall be used. Do you consider the above mentioned too complex and maybe creating bad readability - in other words would you suggest to rely on what PHP serves us with?
1. Could you remind me why you prefix Throwable or Exception with a backslash? I know you mentioned this in a previous video. Thanks! 2. If someone misses a space between `Throwable` and `$e`, will that cause an issue? (Noticed it in an existing file - VSCode with both PHP Code Sniffer and PHP CS Fixer doesn't seem to be complaining).
1. Yes we covered this in namespaces lesson, it will try to load that class from local namespace & fail since you probably won't have Throwable class in your own namespace, so either you have to import it or add backslash to load it from global space. 2. Honestly I did not know that this was allowed, I would not rely on it though and just always include the space
Thanks for the video. If I have my whole application code inside try/catch block with Throable, is there any reason to use the set_error_handler and/or set_exception_handler ?
Set exception handler is pretty much same as global try/catch. I would use exception handler though just in case some exception isn't caught, it will be surely caught by the exception handler
Set error handler can also catch notice and warnings which you can't catch using try/catch so that's one reason to use it if u want to have custom handling of notice/warnings
Thanks for another great lesson. One question, on 11:09 mark in the video, should we in php7 and php8 always use \Throwable instead of \Exception (in that situation) ?
You're welcome. In general yes, \Throwable is better, but I like to catch specific exceptions so if its an exception about an argument being invalid, I throw InvalidArgumentException & catch that, if its an error during some calculation then I would throw custom exception & catch that and so on. I try to avoid \Exception & \Throwable & be explicit whenever possible. I talk about Exception & Throwable at 15:15. In the example at 11:09 the proper way was right before that at 7:58, at 11:09 I just wanted to show an example of what happens if you catch \Exception
First of all thank you so much for everything. I just have a question regarding the last part of the video where you used static methods, I just wanna know the reason behind using late static binding in the return statements ( return new static('Missing billing info'); ), is it because maybe we will use another class that extends the InvoiceException class, or there is another reason for that ? new self would also be fine here right ?
Hi Gio, Sorry to trouble you, please. May I ask, how do you use the Static Exceptions in try/catch blocks? I have a Database Class, say, In the Constructor, I have this: try { $this->pdo = new PDO (......); } catch (DatabaseException $e) { ???? } In my DatabaseException Class, I have: Public static function ConnectionFailureException() which returns new static('.....');
@@ProgramWithGio Thank you Gio. I watched the clip again. And, it showed the usage when you have a Custom Exception Handler or the default Exception Handler. But, it didn't handle usage of the Static flavor in try/catch blocks.
I mean this way of defining Exceptions Classes: Public static function ConnectionFailureException(){ return new static( .... ); } When I need to throw this Exception in the try block, it's as simple as: throw new Database::ConnectionFailureException(); But, when I have a try/catch block, in the catch block I have: catch( DatabaseException $e){ echo $e->getMessage(); ???? } How should the expression in the catch block be written to utilize the static Exception definition in the catch block? Is it okay to still say the usual $e->getMessage(), $e->getCode(), etc.?
@@NedumEze yea I show such example in the video at that timestamp, it's a static method and then we throw it from the other class. Method is static not the entire class, so you still access the object methods regularly in catch
I made the same as you: Try/Catch blocks with my custom exception class who is an extension of the generic exception class, but it's not working i received an global errorhandler message instead of the exception of my custom class... i dont get how it should work...
Hard to say without seeing the code. Can you push your code to GitHub & send me the link? I can check & help you troubleshoot it. You can also DM me on Twitter 👍
@@ProgramWithGio Here is it github.com/gumanzanoo/php-custom-exception Thank you for your help! Well, I tried to implement in a similar way to what I saw in your video. But if you clone the repository and access the /Exception web route, you will see that the error is returned by the standard ErrorException class instead of my CustomException class which is in the catch block. When I hover over the call of the CustomException class, the IDE shows a message 'Exception 'CustomException' is never thrown in the corresponding 'try' block. I don't know why the catch is not handling the exception with my custom class, because the class extends Exception 😰
@@gustavomanzano3360 the custom exception isn't being thrown from anywhere within the try block so that's why your IDE is graying it out, where are you throwing the exception from?
@@gustavomanzano3360 you don't have custom exception handler defined & not throwing the custom exception from anywhere so that's why it's not working the same way. Try to set it up the same way as it is in the video. DM me on Twitter and I can explain it further if needed
Set an exception handler: set_exception_handler(function (\Throwable $e){ var_dump($e->getMessage()); }); echo array_rand([], 1); but it still shows: Warning: array_rand(): Array is empty in C:\Users\Dell\Desktop\forks\quantum-php-project\public\index.php on line 22
You are on PHP 7.4 probably, I mentioned that at 17:22, it throws exception since PHP8, prior to PHP8 it triggers warning & warnings cant be caught with an exception handler or try/catch block. Warnings & notices can be caught by using the error handler that we discussed in the first section of the course (the procedural way of handling errors).
@@ProgramWithGio Sorry, that was a bit short I guess 😅 - on 19:57 you create a class and shortly later a method via a shortcut. I was wondering what kind of shortcut(s) that was.
