I'm experiencing an issue where Binding a model to a route works in routes.php when using
Route::model('user', 'App\User');
but fails in RouteServiceProvider.php when updating the boot function with
$router->model('user', 'App\User');
From the 5.0 documentation, updating the boot function seems to be the way to go, but in 4.2 documentation using the Route facade seems to be the way to go. Is this a possible bug in 5.0?
Or is there another explanation for the observed difference?
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community