@laravel_idea Why not above the method? Might be out of viewport like this, especially if I have a return type that long enough to move route hint out of the screen
@laravel_idea Love it! Thanks for implementing it for me 💯
@laravel_idea This is the only reason Im still using PHPStorm
@laravel_idea Hit to the method, route URL and name. This is cool.
@laravel_idea Very cool! Does it link to the route definition in the web.php?
@laravel_idea Is it possible you could introduce a fuzzy search for this? E.g. you search by route and it takes you to the controller method. Would save me a ton of time on complex projects
@laravel_idea For someone who’s learning TALL I don’t see anything new ? Can you explain please
@laravel_idea With type hinting, this might get extremely long
@laravel_idea Awesome! Please do not put it above method, there is already lots of stuff there
@laravel_idea It's probably not practical, but I'd love an open route in browser. Obviously params won't work or need defaults, but there's plenty of static routes that I've started adding at link to so I can bounce around quicker.
@laravel_idea That’s pretty nice ! Two questions : will it be enabled in api.php file too ? What if I include some routes in another php file (like this: laraveldaily.com/post/laravel-r…) ? Thanks for your work !
@laravel_idea Controller Inline route definition? Cool. However, if it completely replaces route definition in route files, it's a bit hard to find routes. I would use it to complement route definition in route files
@laravel_idea Would love to see route annotations just natively supported by the framework, but as it isn't, this is a nice stepping stone. Defining your routes alongside controller actions is a nice organisational tool.