From 0819da2f2f9cf47fefc3b5d5beedc4a9e5c37c21 Mon Sep 17 00:00:00 2001 From: Szymon Krajewski Date: Fri, 2 Dec 2016 22:08:06 +0100 Subject: [PATCH] Remove info about Whoops in Laravel --- _posts/09-02-01-Errors.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/_posts/09-02-01-Errors.md b/_posts/09-02-01-Errors.md index fd2bf64e3..a99a9bb33 100644 --- a/_posts/09-02-01-Errors.md +++ b/_posts/09-02-01-Errors.md @@ -131,9 +131,8 @@ PHP is perfectly capable of being an "exception-heavy" programming language, and make the switch. Basically you can throw your "errors" as "exceptions" using the `ErrorException` class, which extends the `Exception` class. -This is a common practice implemented by a large number of modern frameworks such as Symfony and Laravel. By default -Laravel will display all errors as exceptions using the [Whoops!] package if the `app.debug` switch is turned on, then -hide them if the switch is turned off. +This is a common practice implemented by a large number of modern frameworks such as Symfony and Laravel. In debug +mode *(or dev mode)* both of these frameworks will display a nice and clean *stack trace*. By throwing errors as exceptions in development you can handle them better than the usual result, and if you see an exception during development you can wrap it in a catch statement with specific instructions on how to handle the