Laravel structure is able to support routes definition on controller and have the routes file be optional ?

[pedrovian4]

I've always liked the notation way to define routes like Symfony, I think in large projects it helps to find things easy. I know we have debugbar and other tools to improve our track, but somehow still helps the route definition on the controller. I have looked the structure of routes definition, and sounds possible to implements, but would it be able to be in framework in the future? What the community thinks about.

[shaedrich]

Sounds like a nice counterpart to contextual attributes 👍🏻

[macropay-solutions]

The laravel community will love it. A niche of developers will hate it.

Question is: Will you still use laravel when it becomes like symfony?

[pedrovian4]

Well I think routes on controller wouldn't make laravel turn into symfony, I mean the laravel way would still be preserved