Container dependency about route

[philipobenito]

This is a simple question of barrier to entry that's been discussed many times.

Whilst I agree with you that in an ideal world the dependency would not be directly on league/container, I disagree that it would increase uptake, I think it would be the opposite.

The recent change to PSR-7 dependency with no implementation is already a larger barrier to entry than I'd like in a perfect world, but it is ultimately a necessary evil, more so than the removal of league/container.

Instantiation is inexpensive so I don't really see that as too much of an issue. Specifically, the league ContainerInterface is used instead of container interoperability because of the reliance on the call method, a bridge can still easily be written though if that initial instantiation bothers you. Otherwise, any container can be used directly with a custom strategy as you're already aware.

I thank you for your input, however, as also discussed on other threads, this isn't something I will be changing for the upcoming major release. It will be reevaluated at the time of the next major release.