by Devin Yang
(This article was automatically translated.)

Published - 8 years ago ( Updated - 8 years ago )

Whoops is a nice little library that helps you better develop and maintain your projects, helping you handle errors and exceptions in a less painful way.
, it was preloaded in Laravel 4, but it was removed in Laravel 5.0, and now 5.5 is back....


Some features of Whoops include:

- Flexible, stack-based error handling
- No dependencies are required to use the current stand-alone library
- Simple API for handling exceptions, tracking frames and their data
-Include a stunning error page within your web application
- Includes the ability to open referenced files directly in editors and IDEs
- Includes handlers for different response formats (JSON, XML, SOAP)
-Easy to extend and integrate with existing libraries
- Clean, well-structured and proven codebase
 

 

Tags: laravel woops

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

Similar Stories


laravel

After upgrading Laravel 8.8, I integrated the articles and notes together

Laravel 8 has undergone major revisions, and my website has also been revised accordingly. The "notes" and "articles" on my website were originally separated into two blocks. This time I integrated him together. Anyway, there are not many articles, and the combined content seems to be more. :p

docker,dlaravel

D-Laravel 1.5.5 Change Notes

D-Laravel's fpm image was rebuilt using the official dockerfile of docker php before php 7.2.1. And so I can specify that the default owner of fpm is dlaravel, --with-fpm-user=USER Set the user for php-fpm to run as. (default: nobody) --with-fpm-group=GRP Set the group for php-fpm to run as.

laravel,oauth2

My most used Laravel passport directives

Laravel provides quite a lot of useful packages, such as Passport is one of them, when the website needs to set up its own OAuth2 authentication host, it really saves time and effort. Take this site as an example, because the front-end and back-end separation mechanisms are adopted (there are two different Laravel projects), and I verify them through the front-end WEB. Basically, I have many other different projects, and they all rely on OAuth2 provided by Laravel to handle cross-domain authentication.