Enhance routing with config options about fortify

[undjike]

I'm facing a similar problem. I want to populate Fortify Routes in a route group to enable route globalization. For instance...

Route::localized(function () {
     // Fortify Routes here
});

[paras-malhotra]

See laravel/jetstream#67, #13 and #15

[MarkIvanowich]

If the user does enable a prefix, then all the current view paths / links will break.

We could leave this as the user's responsibility to publish and edit. Or we could replace the current static paths with route names:

        {{--<form method="POST" action="/login">--}}
        <form method="POST" action="{{route('login')}}">
            @csrf
            ...

[thecodemill]

Still experimenting, but what I've done is:

app/Providers/FortifyServiceProvider.php

public function register()
{
    Fortify::ignoreRoutes();
}

routes/web.php

Route::prefix('auth')->group(function () {
    require base_path('vendor/laravel/fortify/routes/routes.php');
});

Or you could redefine the routes entirely instead of requiring them.

EDIT: Trying to get past the hard-coded route name in Laravel\Fortify\Http\Responses\PasswordResetResponse::toResponse() is proving tricky.

[c0nst4ntin]

@thecodemill have you continued this approach or found a different way?