Hi, Rob!
Good point! I also know one another case when empty catch block are useful.
When we want to avoid returning null values, we resort to using exceptions
so that the client code can somehow handle the absence of values.
For example:
if ($user->getName() !== null) {
$this->doSomethingWithUserName($user->getName());
}
We usually add an exception inside such getters if there is no value:
try {
$this->doSomethingWithUserName($user->getName());
} catch (UserNameIsNull);
This is useful when we need to "do nothing" when there is no value. In my
opinion, this code looks more declarative.
We can do something like this also with repositories:
try {
$post = $this->postRepository->get($postId);
// do something with post
} catch (PostNotFound);
But again, there is a fine line between situations where an empty body of a
catch block is reasonable and when it is not.
чт, 31 июл. 2025 г. в 12:13, Rob Landers <rob@bottled.codes>:
> even in my case, my empty catches have lengthy comments describing why
> they are empty in case a user steps into it, so they can better understand
> how the framework works.
>
> — Rob
>
