-
-
Notifications
You must be signed in to change notification settings - Fork 301
Open
Description
I noticed that calling redirect
in routes causes log lines that are not handled by Lograge. For example:
Route:
get '/old-page', to: redirect('/new-page')
Log output:
Redirected to http://localhost:3000/new-page
Completed 301 Moved Permanently in 1ms
The README indicates redirect_to
in controllers is hooked by lograge. Is it intentional that redirect
in routes is not handled or is it possible for lograge to handle this?
Metadata
Metadata
Assignees
Labels
No labels