This is quite unfortunate, I'd be curious to hear the motivation behind this decision. /cc @taylorotwell

@igorw I've talked w/ @taylorotwell some. Would be good to see some reasoning posted here for posterity but I don't want to put words in his mouth. :)

Primary reason is by not imposing any requirements on the
middleware's constructors we can more cleanly resolve them out of the IoC
container with auto dependency resolution.

On Saturday, December 13, 2014, Beau Simensen notifications@github.com
wrote:

@igorw https://github.com/igorw I've talked w/ @taylorotwell
https://github.com/taylorotwell some. Would be good to see some
reasoning posted here for posterity but I don't want to put words in his
mouth. :)

—
Reply to this email directly or view it on GitHub
#22 (comment).

@taylorotwell can you give an example of how this would be an issue? With a tiny bit of wiring it should be possible to get middlewares constructed by a DIC.

PS: I respect your decision to no longer use it. I can accept if it was done to remove conceptual overhead, because I do get that stack adds concepts. And the APIs are not necessarily in line with what laravel has to offer, etc. There are many social reasons not to use stack.

I would just appreciate to know technical reasons if they do exist, so we can come up with solutions for them.