Maybe it's not the Symfony way, but a bit of another proposal.

// opt-out from exception to manually check
$data = $response->toArray(false);

if ($response->status()->isNotFound()) {
    // not found
}

Maybe it's not the Symfony way, but a bit of another proposal.

// opt-out from exception to manually check
$data = $response->toArray(false);

if ($response->status()->isNotFound()) {
    // not found
}

Let's see what others think. The implementation will be different in this case. I think this way is simpler and more straightforward.

I understand the motivation for this PR, but it has a major drawback: the added methods are not discoverable : since the methods are not in ResponseInterface, no IDE nor static analyzer will be able to know about them - and no human reader either.

It will work "by chance", since no base contracts will ensure these methods are actually present on returned response objects.

We could add them on ResponseInterface, but I'd be against it: HTTP status codes are even more standard stuff than any abstraction, so we recommend using them directly instead.

If you really want that experience, I'd suggest using a static class with helpers instead:

HttpStatus::isForbidden($response->getStatusCode())

(I'm not suggesting to add this helper to Symfony either ;))

Closing therefor. Thanks for your understanding and thanks for proposing!