Clearing Ray output
Frequent Ray calls can lead to a long and cluttered Ray log. However, you can take control of the log and clear it at various tages of the application and testing lifecycle.
Zuzana
Shining a light on internals and updates.
Frequent Ray calls can lead to a long and cluttered Ray log. However, you can take control of the log and clear it at various tages of the application and testing lifecycle.
Zuzana
Use Ray to look where your code is called and how many times.
Zuzana
Don't let debugging get to you, let's celebrate!
Zuzana
Laravel 11 recently introduced a nice new feature called Context. We’ve updated Ray with a convenient method to display all set context.
Freek
We recently revamped our Ray documentation. The goal was to give the docs a new home on the myray.app domain and make them easier to navigate by totally overhauling their structure and content. This blog post will give an overview of some packages, technologies, and techniques we used.
Tim
We just released our new Ray docs, check 'em out if you haven't already! They're hosted right here on myray.app and are extra snappy because they use Livewire's navigate feature. Here's how we added wire:navigate to all the links in our docs.
Sebastian
Customizing Ray's output window.
Zuzana
This solves the problem of you forgetting to manually remove ray calls in your code base.
Tim
Pest is an excellent test runner for PHP, that’s been getting more popular. It offers a developer friendly way of writing tests. At Spatie, we use it for all our projects. Did you know that Pest comes with Ray support out of the box? Let’s take a look at this very simple test from one of our own packages.
Freek
Whether you're building a shiny new feature or refactoring a bug deep in a legacy codebase, before you merge your work to production you want to get rid of all those ray() calls you littered the codebase with. You'll probably get rid of most of them on time, but every now and then a stray call gets forgotten during code review.
Sebastian
Using a bit of AppleScript, you can automatically start the Ray desktop app from your PHP code.
Freek
Methods that get called in a bunch of different places can be tricky to debug. Find out where your methods are called with debug_backtrace().
Sebastian
Learn how to detect and resolve N+1 issues in your Laravel project by using Ray.
Tim
Ray has a few tricks up its sleeve to make debugging Livewire components very easy. Let's take a look!
Freek
Ray is a great companion when debugging a test. However, in busy integration tests it can be hard to find out which logs matter and which don’t.
Sebastian
We've added a new method that makes it easier to inspect the content of objects and arrays.
Sam
Freek
At Spatie, we keep working on Ray continuously. We’re adding small quality-of-life improvements every week. We’re happy to announce that you can now copy logged arrays and objects to your clipboard from Ray.
Tim
Database queries are often one of the main bottlenecks when it comes down to your app’s speed. Not only is it important to give your users a snappy experience of your app, slow queries can cause major problems when your app is experiencing high load. Luckily Ray makes it super easy to find out what queries you should optimize.
Tim
One of the most valuable features of Ray is its ability to preview emails in your local environment. This feature will also help you test entire mail flows.
Freek
Next.js development comes with a unique challenge when it comes to debug logging. With different rendering options and environments, I've found myself switching between the node.js developer console and the browser console too many times.
Sam
Understand and fix bugs faster
Ray is a desktop application that serves as the dedicated home for debugging output. Send, format and filter debug information from both local projects and remote servers.