Closed leo95batista closed 3 years ago
When I disable all the features within the fortify.php configuration file
fortify.php
'features' => [ // ],
the default Fortify routes are disabled, but the password confirmation route is still enabled. Is this a bug, or is it intentionally defined that way?
password confirmation route
laraven new app
composer require laravel/fortify
php artisan vendor:publish --provider="Laravel\Fortify\FortifyServiceProvider"
config/fortify.php
features
php artisan route:list
I think there should be a conditional that groups these routes in the routes.php file.
routes.php
https://github.com/laravel/fortify/blob/77bd46ac1729939a8db97b890a4d752dce79dc53/routes/routes.php#L95-L104
Make sure you've cached your config and routes after making those changes.
php artisan config:cache Then: php artisan route:cache
php artisan config:cache
php artisan route:cache
Sounds like a feature request. Feel free to PR something 👍
Description:
When I disable all the features within the
fortify.php
configuration filethe default Fortify routes are disabled, but the
password confirmation route
is still enabled. Is this a bug, or is it intentionally defined that way?Steps To Reproduce:
laraven new app
composer require laravel/fortify
php artisan vendor:publish --provider="Laravel\Fortify\FortifyServiceProvider"
config/fortify.php
and remove all keys withinfeatures
arrayphp artisan route:list
I think there should be a conditional that groups these routes in the
routes.php
file.https://github.com/laravel/fortify/blob/77bd46ac1729939a8db97b890a4d752dce79dc53/routes/routes.php#L95-L104