rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Display exceptions in text format for xhr request	Kir Shatrov	2013-08-22	1	-30/+0
\|
*	Escape the message of an exception in debug_exceptions to avoid bad rendering	Adrien Siami	2013-08-21	1	-1/+1
\|
*	change useless gsub to tr	robertomiranda	2013-03-05	1	-1/+1
\|
*	Move table routes formatter class to the inspector and rename it	Carlos Antonio da Silva	2013-01-06	1	-1/+1
\| \| \| \| \| \| \|	It feels more consistent to have this class called "HtmlTableFormatter", and to have it here with the routes inspector and console formatter, since it's used for both routing error exceptions and the rails info page.
*	Close container div tag in routing error page	Carlos Antonio da Silva	2013-01-05	1	-9/+11
\|
*	display mountable engine routes on RoutingError.	Yves Senn	2013-01-05	1	-2/+2
\|
*	Remove unnecessary `ERB::Util::h`	Ryunosuke SATO	2013-01-05	1	-2/+2
\| \| \| \|	It is automatically applied when strings is unsafe for html.
*	Add new style to Routing Error page	Guillermo Iguaran	2012-12-31	1	-19/+22
\|
*	Format routes as html on debug page	schneems	2012-12-17	1	-1/+3
\| \| \| \| \| \| \| \| \|	When someone gets a routing exception, the routes are rendered (starting in Rails 4.0). This PR brings parity between the html routes in the `rails/info/routes` path and when rendered from an exception. This is the continuation of #8521 which brought html formatted routes. In addition to bringing parity to the two views, we're keeping our views DRY by rendering off of the same partials. In this case Railties depends on partials provided by ActionDispatch. I'm open to alternative implementations. Ideally both views will use the same code so any improvements or updates to it will be reproduced on both. <hr /> ![](http://f.cl.ly/items/3O1D0K1v0j0i343O3T3T/Screen%20Shot%202012-12-17%20at%203.07.20%20PM.png)
*	1.9 hash syntax changes to docs	AvnerCohen	2012-10-31	1	-1/+1
\|
*	show routes while debugging RoutingError	schneems	2012-07-07	1	-2/+8
\| \| \| \|	If someone receives a routing error, they likely need to view the routes. Rather than making them visit '/rails/info/routes' or run `rake routes` we can give them that information on the page.
*	Add backtrace to development routing error page	schneems	2012-05-02	1	-1/+3
\| \| \| \| \| \|	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.
*	add help text to routing error	schneems	2011-12-17	1	-8/+13
\| \| \| \| \| \|	When a newcomer hits the routing error page they are often confused about how to trouble shoot the next step. Adding a simple help text can gently remind coders where to get more help.
*	Extract ActionController rescue templates into Rescue and ShowExceptions ↵	Joshua Peek	2009-05-02	1	-0/+10
	middleware. This commit breaks all exception catching plugins like ExceptionNotifier. These plugins should be rewritten as middleware instead overriding Controller#rescue_action_in_public.