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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Change filter on /rails/info/routes to use an actual path regexp from rails	brainopia	2015-02-23	2	-67/+63
\| \| \| \| \| \| \| \|	Change filter on /rails/info/routes to use an actual path regexp from rails and not approximate javascript version. Oniguruma supports much more extensive list of features than javascript regexp engine. Fixes #18402.
*	Don't center the routes table on routing errors	Genadi Samokovarov	2014-11-24	1	-1/+1
\|
*	Escape user input before showing in the page.	Rafael Mendonça França	2014-05-26	1	-2/+2
\| \| \| \| \| \|	This is not a security issue since this page is not present in production and user have to type something in the field but is better to escape the input.
*	Split search results into 'exact matches' and 'fuzzy matches'.	Winston	2014-04-11	1	-60/+96
\| \| \| \|	- also refactored the javascript.
*	Improve CSS styling for routing error html page.	Winston	2014-04-11	1	-7/+25
\|
*	Implement fuzzy matching for route search on routing error html page.	Winston	2014-04-11	1	-8/+10
\|
*	Spelling and Grammar checks	Akshay Vishnoi	2013-12-12	1	-2/+2
\|
*	In Browser Path Matching with Javascript	schneems	2013-01-20	2	-11/+99
\| \| \| \| \| \| \| \| \| \| \|	When debugging routes ,it can sometimes be difficult to understand exactly how the paths are matched. This PR adds a JS based path matching widget to the `/rails/info/routes` output. You can enter in a path, and it will tell you which of the routes that path matches, while preserving order (top match wins). The matching widget in action: ![](http://f.cl.ly/items/3A2F0v2m3m1Z1p3P3O3k/path-match.gif) Prior to this PR the only way to check matching paths is via mental math, or typing in a path in the url bar and seeing where it goes. This feature will be an invaluable debugging tool by dramatically decreasing the time needed to check a path match. ATP actionpack
*	Rename route_wrapper partial layout to table	Carlos Antonio da Silva	2013-01-06	1	-0/+0
\| \| \| \| \| \|	It is used by the table formatter only, and it's already inside a routes directory that namespaces it properly, so calling it just "table" seems simpler.
*	Move style to head to make routes page valid html5	Carlos Antonio da Silva	2013-01-05	1	-4/+4
\|
*	Minor js review [ci skip]	Carlos Antonio da Silva	2012-12-18	1	-7/+7
\| \| \| \|	Remove/add ; where necessary, fix indentation.
*	Format routes as html on debug page	schneems	2012-12-17	2	-0/+72
	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)