Elegant Pipeline Cleanup with Laravel's finally Method
The new finally method simplifies how you handle post-pipeline operations, whether your pipeline succeeds or fails.
Read more [www.harrisrafto.eu]
Posts tagged with error handling
When everything fails, you can always trust the Laravel rescue helper
– flareapp.io - submitted by Spatie
Read more [flareapp.io]
Join thousands of developers
Every two weeks, I share practical tips, tutorials, and behind-the-scenes insights from maintaining 300+ open source packages.
No spam. Unsubscribe anytime. You can also follow me on X.
A package to display solutions on the Laravel error page
When Laravel switched to a simpler exception page, the ability to display solutions for an exception was lost.
Our latest package, called spatie/laravel-error-solutions brings back that powerful feature. When installed, it will display solutions for most common exceptions.
Here’s how that looks it:
And yes, some solutions, like the one in the screenshot above, can be executed on the exception page too.
In this blog post, I’d like to tell you all about it!
Building Laravel Error Share
Here's how our latest package works under the hood.
Read more [sebastiandedeyne.com]
Introducing Laravel Error Share
– flareapp.io - submitted by Spatie
Introducing Laravel Error Share, simply share and debug local errors with your team!
Read more [flareapp.io]
Assigning a user to an error
– flareapp.io - submitted by Spatie
Learn how you can assign a user to an error in Flare!
Read more [flareapp.io]
Ignition and Flare can now display Laravel 11's context
– flareapp.io - submitted by Spatie
Ignition got a little bit better again.
Read more [flareapp.io]
Enhancing error reporting with custom context and glows
– flareapp.io - submitted by Spatie
Learn how to improve your debugging experience with custom context and glows.
Read more [flareapp.io]
Retry mechanisms in Laravel
– ahmedshamim.com - submitted by Ahmed Shamim
Laravel provides some excellent 'Retry' mechanisms out of the box for handling transient failures! In this article, we'll learn about these mechanisms to build a reliable system using Laravel!
Read more [ahmedshamim.com]
Improved handling of 404 errors with Livewire
– srwiez.com - submitted by Eser DENIZ
I like to use the findOrFail() function in Livewire methods that call actions. But I really don't like the default behaviour of Livewire showing a modal view with a 404. Let me show you how to personalise that.
Read more [srwiez.com]
Introducing Jira Integration with Flare
– flareapp.io - submitted by Spatie
Learn how to connect your Flare errors with Jira issues
Read more [flareapp.io]
Why error tracking is crucial for your application
– flareapp.io - submitted by Spatie
Alex and Christoph explain why error tracking is crucial for your application.
Read more [flareapp.io]
Flare and Ignition now offer AI-powered solutions
Today, we're adding AI-powered solutions to Flare. This means we can suggest a solution for almost any error: the AI will likely suggest a helpful suggestion for most errors.
Read more [flareapp.io]
A preview of Flare's upcoming redesign
My colleagues and I are hard at work making the best error tracker for Laravel even better.
Read more [flareapp.io]
A better error page for Symfony applications
Ignition is the most beautiful error page for PHP apps. Yesterday, we launched a new major version of Ignition - you can check out all the details in this blog post.
Ignition used to be Laravel specific, but we've now created a framework agnostic version as well. Let's try using Ignition in a simple Symfony app.
Linking to Flare errors on your error page
We've launched a new feature that will make it easier for users of your app to report specific errors.
Read more [flareapp.io]
JSON API Error Responses in Laravel with Httpable Exceptions
Jess Archer show a nice approach on how to use exception in the HTTP layer.
Read more [jessarcher.com]
A new design for Ignition
A couple of years ago, Ignition became the default error page in Laravel.
Ignition provided a vastly improved design over Whoops: it brought Laravel specific niceties (such as showing the routing, queries) and the ability to display and even run solutions (e.g. generating an app key).
At Spatie, we think we can improve the design of Ignition even more. Our initial plan was to release this new design in tandem with Laravel 9 as a big bang surprise release. We've changed our mind on this because we'd like to have feedback from the community.
In this blog post, I'd like to share our ideas and plans for Ignition.
The magic of dedicated exception classes
You can make your code more readable by moving all your exception messages to dedicated classes. We using this technique in all our projects and packages.
Dealing with expired signed URLs in Laravel
Out of the box, Laravel comes with the ability to generate "signed" URLs. These URLs have a hash in their query string that verifies that the URL was not modified.
At Flare, we use these signed URLs to add action links in mail notifications. The action links allow users to snooze and resolve errors right from the mail without having to be logged in. Pretty convenient!
My buddy Dries Vints noticed a slight drawback. He got a mail from Flare that contains these action links. A few hours after the mail arrived, he clicked one of the action links. This is what he saw.