You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/09-02-01-Errors.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,9 @@ make the switch. Basically you can throw your "errors" as "exceptions" using the
132
132
the `Exception` class.
133
133
134
134
This is a common practice implemented by a large number of modern frameworks such as Symfony and Laravel. In debug
135
-
mode *(or dev mode)* both of these frameworks will display a nice and clean *stack trace*.
135
+
mode *(or dev mode)* both of these frameworks will display a nice and clean *stack trace*.
136
+
137
+
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.
136
138
137
139
By throwing errors as exceptions in development you can handle them better than the usual result, and if you see an
138
140
exception during development you can wrap it in a catch statement with specific instructions on how to handle the
0 commit comments