Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week
Source: stitcher.io
The case for route attributesCategory: Laravel, Laravel, PHP, PHP
Scout APM helps PHP developers pinpoint N+1 queries, memory leaks & more so you can troubleshoot fast & get back to coding faster. Over the years, I've gone from loving them to hating them, to loving them again, to somewhere in between.
One of the only arguments against route attributes that I kind of agree with, is how we deal with collisions.
The most obvious solution is to simply allow some kind of "order" key on route attributes, so that you can carefully control their order yourself: I agree that this approach isn't ideal, but I'd say that solving route collisions never is.
And, secondly: attribute discovery and route registration is something that is very easily cacheable in production: Laravel already does this with event listeners and blade components, just to name two examples.
One of the only arguments against route attributes that I kind of agree with, is how we deal with collisions.
The most obvious solution is to simply allow some kind of "order" key on route attributes, so that you can carefully control their order yourself: I agree that this approach isn't ideal, but I'd say that solving route collisions never is.
And, secondly: attribute discovery and route registration is something that is very easily cacheable in production: Laravel already does this with event listeners and blade components, just to name two examples.
Newsletter
Glimpse
Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge.
Community Partners
Laravel/PHP Careers