Add name_prefix configuration option to Fortify

Author: Sagmedjo

config/fortify.php

@@ -12,6 +12,7 @@
     'views' => true,
     'home' => '/home',
     'prefix' => '',
+    'name_prefix' => '',
     'domain' => null,
     'lowercase_usernames' => false,
     'limiters' => [

src/FortifyServiceProvider.php

@@ -7,6 +7,7 @@
 use Illuminate\Support\Facades\Auth;
 use Illuminate\Support\Facades\Route;
 use Illuminate\Support\ServiceProvider;
+use Illuminate\Support\Str;
 use Laravel\Fortify\Actions\RedirectIfTwoFactorAuthenticatable;
 use Laravel\Fortify\Contracts\EmailVerificationNotificationSentResponse as EmailVerificationNotificationSentResponseContract;
 use Laravel\Fortify\Contracts\FailedPasswordConfirmationResponse as FailedPasswordConfirmationResponseContract;
@@ -158,11 +159,15 @@ protected function configurePublishing()
      */
     protected function configureRoutes()
     {
+        $as = config('fortify.name_prefix', '');
+        $as = $as !== '' ? Str::finish($as, '.') : '';
+
         if (Fortify::$registersRoutes) {
             Route::group([
                 'namespace' => 'Laravel\Fortify\Http\Controllers',
                 'domain' => config('fortify.domain', null),
                 'prefix' => config('fortify.prefix'),
+                'as' => $as,
             ], function () {
                 $this->loadRoutesFrom(__DIR__.'/../routes/routes.php');
             });

stubs/fortify.php

@@ -81,13 +81,15 @@
     |--------------------------------------------------------------------------
     |
     | Here you may specify which prefix Fortify will assign to all the routes
-    | that it registers with the application. If necessary, you may change
-    | subdomain under which all of the Fortify routes will be available.
+    | that it registers in the application. You may also give a route name
+    | prefix and the subdomain under which all the Fortify routes exist.
     |
     */
 
     'prefix' => '',
 
+    'name_prefix' => '',
+
     'domain' => null,
 
     /*