From 165f7f9bc894d7e77cd6626e555d44b3060c6698 Mon Sep 17 00:00:00 2001 From: Kushal Date: Wed, 14 Jun 2017 13:50:10 +0530 Subject: [PATCH] Create 09-02-01-Errors.md --- _posts/09-02-01-Errors.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/_posts/09-02-01-Errors.md b/_posts/09-02-01-Errors.md index a99a9bb..c510a70 100644 --- a/_posts/09-02-01-Errors.md +++ b/_posts/09-02-01-Errors.md @@ -132,7 +132,9 @@ make the switch. Basically you can throw your "errors" as "exceptions" using the the `Exception` class. 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*. +mode *(or dev mode)* both of these frameworks will display a nice and clean *stack trace*. + +There are also some packages available for better error and exception handling and reporting. Like [Whoops!], which comes with the default installation of Laravel and can be used in any framework as well. 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