If your eyes can't handle our light design, you may prefer our soothing dark mode. When clicking save in the dialog, we'll create or update that configuration file for you. In the previous version of Ignition, you had to edit a configuration file to set these options. Here you can choose the editor that will open when clicking a line in the stack trace (more on that in a bit), and you can also choose the theme. When you click it, the settings dialog open. Next to the docs link, you'll see the cogwheel. Determining which docs page is opened for an exception is handled by the LaravelDocumentationFinder class. Have an exception using a collection, then we'll redirect you to the available collection methods docs. If you have an exception executing a query, we'll put a link to the Eloquent docs. When we've found an exact page, we'll display a red dot at that docs menu item. If you get a Laravel specific error, we'll try to determine a more exact page in the docs. ![]() So, in Laravel 8, it'll link to this page by default. ![]() The docs item will link to the documentation of the Laravel release you're currently using. You'll see any new "Docs" link in the top right corner. This means that you can now either use the links at to top to get to the section you want, or you could manually scroll down. We've switched from a tabbed layout to a single page with an active scroll indicator. Ignition has been redesigned from the ground up, fixing many of the minor paper cuts in the previous design. After that, an exception will be instantly recognisable again. Work on this is well underway, we need a couple of weeks to fine-tune and launch this design at Flare. This is how Ignition looks like in Laravel 9.įlare hasn't adopted this new design just yet. To keep our UI recognisable for Flare users, we had to redesign Ignition as well.Įarly in 2020, we decided that Laravel 9 would be the perfect opportunity to launch the new design. Even though Flare looked good on the day we launched it, we felt it was time to refresh Flare's UI. Three years is a very long time on the internet. Here's how an exception looks like in Flare.Ī universal truth is that everything will eventually change (except maybe the speed of light). When you use Flare, you'll feel right at home, making Flare easy to use. You'll notice that Flare looks a lot like Ignition. The first version of Ignition could do a lot of Laravel specific things: it shows you the current route and middleware, it shows you the original Blade views (when there's a view error), it can run Laravel specific solutions (such as generating an app key when it is missing), and much more. Here's how the first version of Ignition looks like (you probably recognise it, as it's the current default error page in Laravel). When creating Flare, we went the extra mile and made a beautiful Laravel specific error page called Ignition. It's a framework-agnostic package, so it doesn't report on any Laravel specific bits. ![]() We thought that Whoops was nice, but also that it had some room for improvement. If you've been using Laravel for some time, you'll probably still recognise it. At the time, Laravel was still using the Whoops. When creating Flare, one of our goals was to launch the best-looking error tracker. ![]() Three years ago, our team launched Flare, the best error tracker service for Laravel apps. In this stream on YouTube, I gave a tour of all Ignition features! Have a look! A little bit of history repeating In this blog post, I'd like to tell you all about it. You can optionally install it into any Laravel 8 or framework-agnostic app. This error page will be the default in Laravel 9. It has been redesigned from the ground up. I'm proud to share that our team has released a new major version of Ignition, the most beautiful error page for Laravel and PHP.
0 Comments
Leave a Reply. |