Laravel's "rescue" Helper Function is Amazing

March 23, 2022

The rescue function is an alternative to the traditional try/catch block syntax required when you want to manually handle a thrown exception. It takes a callback and executes it inside of a try block for you. The result of the callback will be returned if no exception is thrown.

Let’s look at a typical use-case of a try/catch block.

1$country = 'USA';
3try {
4 $alpha2 = (new ISO3166)->alpha3($country)['alpha2'];
5} catch (\Exception $e) {
6 $alpha2 = null;


What an ugly piece of code for something that is really quite simple.

rescue to the rescue

Now let’s see that using our fancy new rescue function.

1$alpha2 = rescue(fn () => (new ISO3166)->alpha3($country)['alpha2']);

What happens here is when the callback executes without an exception being thrown, what’s returned from the callback is assigned to our $alpha2 variable. If an exception is thrown, $alpha2 is assigned null.

But what if you don’t want the value to be assigned null? Well, you have some options.

First, you can return a different value. For example, you may want to get false back instead. That’s where rescue’s second parameter comes in:

1$isFalse = rescue(function () {
2 throw new Exception;
3}, false);

Second, you can make the second parameter a callback, where you can do anything you’d normally do inside of a catch block, and whatever is returned from that callback is returned from rescue if an exception is thrown. You’ll even get the exception as an argument to your callback.

1rescue(function () {
2 throw new Exception;
3}, function ($e) {
4 // do exception related stuff
6 return false;
9// => false

I don’t think this function adds a ton of utility when you’re in a situation where you’re passing two callbacks to it. However, when you just want to attempt to do something in your first callback and get a different value if it fails, rescue is a handy little helper function.

In my opinion, functions like rescue are what make programming fun. They strip away the syntax-y parts that are distracting, and can leave you with a clean block of code that focuses on what it’s actually doing. It’s the epitome of clean code. A simple, reusable, beautiful, little function that allows you to ditch the hideousness of the try/catch block when you can.

For your reading pleasure, here is a real, live coding sample that I’ve written.

1public function getCountryByFormat(string $country, CountryFormat $format): array|null
3 return rescue(fn () => match ($format) {
4 CountryFormat::NAME => (new ISO3166)->name($country),
5 CountryFormat::ALPHA_2 => (new ISO3166)->alpha2($country),
6 CountryFormat::ALPHA_3 => (new ISO3166)->alpha3($country),
7 CountryFormat::NUMERIC => (new ISO3166)->numeric($country),
8 }, null, false);

NOTE: That third parameter of false tells the function not to report the exception to the error logger. Since we are kind of expecting this exception, we don’t want to report it. Watch out for that potential gotcha.

For comparison’s sake, here’s what it would look like in a try/catch block.

1public function getCountryByFormat(string $country, CountryFormat $format): array|null
3 try {
4 return match ($format) {
5 CountryFormat::NAME => (new ISO3166)->name($country),
6 CountryFormat::ALPHA_2 => (new ISO3166)->alpha2($country),
7 CountryFormat::ALPHA_3 => (new ISO3166)->alpha3($country),
8 CountryFormat::NUMERIC => (new ISO3166)->numeric($country),
9 };
10 } catch (\Exception $e) {
11 return null;
12 }

A pretty sweet improvement if you ask me. Thanks Taylor Otwell!

Now that you know about rescue, I expect you’ll be using it all over the place like me. Enjoy!