Add backtrace to development routing error page #6131

Merged
merged 1 commit into from May 3, 2012

Conversation

Projects
None yet
5 participants
Member

schneems commented May 2, 2012

If a user gets a routing error due to a view helper such as using user_path without an :id they must go to their logs to see the backtrace. By adding in the trace template, a user can see which line the error occurred on without leaving the browser.

When a routing error occurs outside of the view the application trace will be blank and will not confuse developers.

Before PR: http://cl.ly/3x332b0V2d0E0Q1G0C1t
After PR: http://cl.ly/2O431D0A1u2Q2p130A3t

Add backtrace to development routing error page
If a user gets a routing error due to a view helper such as using user_path without an :id they must go to their logs to see the backtrace. By adding in the trace template, a user can see which line the error occurred on without leaving the browser.

When a routing error occurs outside of the view the application trace will be blank and will not confuse developers.
Contributor

qrush commented May 2, 2012

Nice!! 👍 💣

Contributor

mcmire commented May 3, 2012

Oh yeah, this is great.

spastorino added a commit that referenced this pull request May 3, 2012

Merge pull request #6131 from schneems/schneems/routes_backtrace
Add backtrace to development routing error page

@spastorino spastorino merged commit b93def9 into rails:master May 3, 2012

@jonleighton jonleighton referenced this pull request in jonleighton/focused_controller Sep 2, 2012

Closed

Weird path bug that displays wrong error #19

kuraga commented Nov 1, 2012

GREAT!!!!!! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment