Slim 5: Enable header manipulation in ErrorRenderer/ErrorHandler about slim HOT 6 CLOSED

just for my information, is there any branch, roadmap or milestone for slim 5?

from slim.

@eerison, there is not an official roadmap for Slim 5. I am just maintaining the many repos of the org and I have a full time job, unfortunately no time for this. If someone wants to step up and take the reigns, they are more than welcome to!

from slim.

I'm a bit confused by this, the error renderer's sole purpose is to render errors.

adding, removing or changing headers should be done within middleware or at the route callback level.

You can implement your own error middleware if needed to accomplish this.

from slim.

I agree that the usage of a ErrorRenderer is to purposefully render an error, but what I meant with this issue was a way to be capable of doing more than just doing the error redering, but I think you're right, I should probably deal with this in the middleware (or on a custom error handler).
The use case I had in mind was around rate-limiting, where I throw an exception that gets rendered by JsonErrorRenderer and lacks the rate-limiting headers.

from slim.

@flavioheleno then I would suggest creating your own responder or error middleware to address this. It's not hard to extend the existing stuff to achieve what you want to do. I'm closing this as resolved.

from slim.