[5.5] Ability to build a response using a fallback route name

[themsaid]

Having:

Route::fallback('ServersController@notFound')->name('notFoundServer');

In your exception handler or inside another route you can do:

return Route::respondWith('notFoundServer');

This will run the ServersController@notFound action and return its response.

This is useful for when you want to catch a ModelNotFound exception and return a fallback route instead of the 404.blade.php view.

[sisve]

Would this support route middlewares like StartSession so we can get session support on the custom 404 pages?

[themsaid]

@sisve yes

[decadence]

@themsaid Is this can be used with any route name?

[browner12]

@decadence I was able to use it with any route name.

[decadence]

@browner12
Any route as long as it doesn't require parameters © @themsaid

[unstoppablecarl]

Where would be the best place to catch response exceptions and return Route::respondWith('notFoundServer'); to override of normal behavior in the whole app?

[themsaid]

@unstoppablecarl the exception handler.