- 23 8月, 2013 1 次提交
-
-
由 Kir Shatrov 提交于
-
- 21 8月, 2013 1 次提交
-
-
由 Adrien Siami 提交于
-
- 03 5月, 2013 1 次提交
-
-
由 Tim Krajcar 提交于
-
- 10 4月, 2013 1 次提交
-
-
由 Nikolay Shebanov 提交于
-
- 09 4月, 2013 2 次提交
-
-
由 Vipul A M 提交于
-
由 Agis Anastasopoulos 提交于
It'd be a nice convention to mark the unused variables like this, now that Ruby 2 will issue no warnings for such vars being unused.
-
- 07 3月, 2013 1 次提交
-
-
由 robertomiranda 提交于
-
- 05 3月, 2013 1 次提交
-
-
由 robertomiranda 提交于
-
- 18 2月, 2013 1 次提交
-
-
由 Bartlomiej Kozal 提交于
-
- 21 1月, 2013 1 次提交
-
-
由 schneems 提交于
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:  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
-
- 06 1月, 2013 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
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.
-
由 Carlos Antonio da Silva 提交于
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.
-
- 05 1月, 2013 3 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
由 Carlos Antonio da Silva 提交于
-
由 Yves Senn 提交于
-
- 04 1月, 2013 2 次提交
-
-
由 Ryunosuke SATO 提交于
It is automatically applied when strings is unsafe for html.
-
由 Gosha Arinich 提交于
-
- 03 1月, 2013 3 次提交
-
-
由 Gosha Arinich 提交于
-
由 Guillermo Iguaran 提交于
-
由 Sam Ruby 提交于
* <pre> is not allowed to be nested inside of <p> elements in HTML * Indentation of </p> doesn't match corresponding <p> * <p> element not explicitly closed * One more </div> than <div> In each case, the template was fixed to match how a HTML5 parser would "see" the resulting page.
-
- 02 1月, 2013 4 次提交
-
-
由 Lucas Mazza 提交于
-
由 Gosha Arinich 提交于
-
由 Gosha Arinich 提交于
-
由 Guillermo Iguaran 提交于
-
- 01 1月, 2013 6 次提交
-
-
由 Guillermo Iguaran 提交于
-
由 Guillermo Iguaran 提交于
-
由 Guillermo Iguaran 提交于
-
由 Guillermo Iguaran 提交于
-
由 Guillermo Iguaran 提交于
-
由 Guillermo Iguaran 提交于
-
- 18 12月, 2012 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
Remove/add ; where necessary, fix indentation.
-
由 schneems 提交于
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 /> 
-
- 01 11月, 2012 1 次提交
-
-
由 AvnerCohen 提交于
-
- 08 7月, 2012 1 次提交
-
-
由 schneems 提交于
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.
-
- 05 5月, 2012 1 次提交
-
-
由 Piotr Sarnacki 提交于
SessionStore was recently changed to delegate to hash object instead of inherit from it. Since we don't want to extend SessionStore with every method implemented in Hash, it's better to just convert any object passed to debug_hash (which is also better as we don't require to pass Hash instance there, it can be any object that can be converted to Hash).
-
- 03 5月, 2012 1 次提交
-
-
由 schneems 提交于
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.
-
- 18 12月, 2011 1 次提交
-
-
由 schneems 提交于
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.
-
- 03 11月, 2011 1 次提交
-
-
由 Olivier Lacan 提交于
Using the white-space: pre-wrap adds extra line breaks to prevent the text from breaking out of the element's box. In this case single line output can be extremely long, breaking out the <body> element. See for reference: http://www.quirksmode.org/css/whitespace.html Before: http://link.olivierlacan.com/BVU4 After: http://link.olivierlacan.com/BUfM
-
- 06 5月, 2011 1 次提交
-
-
由 José Valim 提交于
-
- 05 5月, 2011 1 次提交
-
-
由 David Heinemeier Hansson 提交于
-