I'm working with Laravel 8 and when I write the route to the __invoke
controller like this:
use App\Http\Controllers\PortfolioController;
Route::get('/portfolio', 'PortfolioController')->name('portfolio');
It shows this error:
Invalid route action: [PortfolioController].
PortfolioController
is not invokable
So it only works like this:
Route::get('/portfolio', [PortfolioController::class, '__invoke'])->name('portfolio');;
Which doesn't make sense to me because it should find the __invoke
which is the only one in PortfolioController.php
:
namespace App\Http\Controllers;
use Illuminate\Http\Request;
class PortfolioController extends Controller
{
/**
* Handle the incoming request.
*
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
*/
public function __invoke(Request $request)
{
$portfolio = [
['title' => 'Project #1'],
['title' => 'Project #2'],
['title' => 'Project #3'],
['title' => 'Project #4'],
];
return view('portfolio',compact('portfolio'));
}
}
Is Laravel 8 ignoring the __invoke
attribute???
Do it like so:
use App\Http\Controllers\PortfolioController;
Route::get('/portfolio', PortfolioController::class)->name('portfolio');
^^^^^^^^^^^^^^^^^^^^^^^^^^
Before Laravel 8, routes were namespaced in RouteServiceProvider.php
:
protected $namespace = 'App\Http\Controllers';
// ...
protected function mapWebRoutes()
{
Route::middleware('web')
->namespace($this->namespace) // <----
->group(base_path('routes/web.php'));
}
So, when you defined routes, like in your example:
Route::get('/portfolio', 'PortfolioController')->name('portfolio');
^^^^^^^^^^^^^^^^^^^^^
The PortfolioController
string were namespaced with App\Http\Controllers
.
In Laravel 8 this behavior has been modified. From the v8 release note:
In Laravel 8.x, this property is
null
by default. This means that no automatic namespace prefixing will be done by Laravel. Therefore, in new Laravel 8.x applications, controller route definitions should be defined using standard PHP callable syntax:use App\Http\Controllers\UserController; Route::get('/users', [UserController::class, 'index']);
Now, for the particular case you mentioned, __invoke()
methods, this is how you should handle them according to the docs:
When registering routes for single action controllers, you do not need to specify a method:
use App\Http\Controllers\ShowProfile; Route::get('user/{id}', ShowProfile::class);
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With