Proposal: Throwable responses

[vlakoff]

Would you be interested in a feature like laravel/framework#13473?

Currently, throwing a response requires the following. As more, SlimException isn't really appropriate.

$response = $response->withRedirect($url);
throw new \Slim\Exception\SlimException($request, $response);

Whereas a few additions would allow to do this:

$response->withRedirect($url)->throwResponse();

Note the request isn't used actually.

[KuroThing]

Exceptions as control flow are generally considered an anti pattern, there is some discussion about it on stackoverflow.

[vlakoff]

Sure thing, but there are exceptions to this. In this situation, exceptions play really nice.

• Otherwise you have to propagate returns all the way up, which sometimes isn't even doable.
• These exceptions allows fine-grained and centralized handling (error handling, logging, and much more).
• Features like Laravel's terminable middlewares free you from the sequential flow constraint.

As a result, you have a really great application flow that wouldn't be possible without these exceptions.

[KuroThing]

And exceptions are not not designed for this kind of control flow.

In a website that has thousands of hits an hour, using Exceptions as Control Flow is terrible performance wise, and doesn't scale. At all.

Why encourage bad design?

[geggleto]

I can't get behind this idea at all.

Throwable response will not work in Slim.

The idea being that you can immediately terminate from the app strikes me as weird as it's you need to go back through your middleware to complete any actions, throwing response breaks that.

[vlakoff]

Populus locutus est, closing as there is a clear consensus, no need to pursue.