| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | UrlGenerationError are not catched as 404 anymore | Jean Boussier | 2014-10-27 | 1 | -1/+1 |
| | | |||||
| * | remain backwards compatible, exception can be constructed with no arguments | Aaron Patterson | 2012-10-25 | 1 | -1/+3 |
| | | |||||
| * | give access to the original exception raised in case of a parse error | Aaron Patterson | 2012-10-25 | 1 | -0/+7 |
| | | |||||
| * | Add Missing Keys from Journey on failed URL format | schneems | 2012-08-28 | 1 | -0/+3 |
| | | | | | | | | | | | | | | | | | | | | | | | | Many named routes have keys that are required to successfully resolve. If a key is left off like this: <%= link_to 'user', user_path %> This will produce an error like this: No route matches {:action=>"show", :controller=>"users"} Since we know that the :id is missing, we can add extra debugging information to the error message. No route matches {:action=>"show", :controller=>"users"} missing required keys: [:id] This will help new and seasoned developers look closer at their parameters. I've also subclassed the routing error to be clear that this error is a result of attempting to generate a url and not because the user is trying to visit a bad url. While this may sound trivial this error message is misleading and confuses most developers. The important part isn't what's in the options its's what's missing. Adding this information to the error message will make debugging much more obvious. This is the sister pull request of https://github.com/rails/journey/pull/44 which will be required to get they missing keys into the correct error message. Example Development Error in Rails: http://cl.ly/image/3S0T0n1T3421 | ||||
| * | Raise ActionController::BadRequest for malformed parameter hashes. | Andrew White | 2012-05-20 | 1 | -1/+4 |
| | | | | | | | | | | | | | | | Currently Rack raises a TypeError when it encounters a malformed or ambiguous hash like `foo[]=bar&foo[4]=bar`. Rather than pass this through to the application this commit captures the exception and re-raises it using a new ActionController::BadRequest exception. The new ActionController::BadRequest exception returns a 400 error instead of the 500 error that would've been returned by the original TypeError. This allows exception notification libraries to ignore these errors if so desired. Closes #3051 | ||||
| * | Raise a rescuable exception when Rails doesn't know what to do with the ↵ | Steven Soroka | 2012-05-06 | 1 | -0/+3 |
| | | | | | format, rather than responding with a head :not_acceptable (406) | ||||
| * | Remove obsolete reader from AC::MethodNotAllowed exception class | Alexey Vakhov | 2012-03-31 | 1 | -2/+0 |
| | | |||||
| * | Remove AC::RenderError class second declaration | Alexey Vakhov | 2012-03-31 | 1 | -3/+0 |
| | | |||||
| * | Remove other old compatibility constants | Carlos Antonio da Silva | 2012-01-17 | 1 | -1/+1 |
| | | |||||
| * | Remove fancy method not allowed resource exceptions since they are | Joshua Peek | 2009-12-11 | 1 | -10/+1 |
| | | | | | too much of a hack | ||||
| * | SessionRestoreError belongs in AD | Joshua Peek | 2009-09-23 | 1 | -3/+0 |
| | | |||||
| * | Rename /base to /metal and make base.rb and metal.rb top-level to reflect ↵ | Yehuda Katz | 2009-08-06 | 1 | -0/+58 |
| their module locations | |||||
 |
index : rails.git | |
| Mirror of official rails repo with custom fixes. | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |