[Proposal] Controllers have the current request as a property

[kapv89]

I know its a bit far off, but currently controllers derive their state via the callAction method. That means that the code beign written in the action cannot be stateless .. ie, all the actions, when called directly, in a newly 'composed' controller, need a global state.

This issue can be easily resolved by the controller having a request and response property in the controller.
The actions read from request and modify the response.
So the closure that the router forms for wrapping a controller action can just instantiate the controller with the current request, let the controller process the response, and then just return it .. what say ?

[bencorlett]

You know what, I've run into this and I love it. Makes unit testing individual package controllers easier outside the scope of Laravel too.

[taylorotwell]

I would prefer to keep controllers how they are.