Solution
It's not a bug. It's expected behaviour.
You don't say, but I assume you're issuing a GET request to http://yoursite.tld/admin/invoice/settings.
In your first example that satisfies the pattern admin/invoice/{resource} which maps to the show() method. This is explained here in the docs.
In the second example, your custom-defined route is the first match giving the result that you were hoping for.
To avoid this sort of confusion, it's generally best to put your most specific route definitions first.
Last updated
2 years ago.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast