- 19 12月, 2013 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
Change most tests to make use of assert_raise returning the raised exception rather than relying on a combination of flunk + rescue to check for exception types/messages.
-
- 06 11月, 2013 1 次提交
-
-
由 Godfrey Chan 提交于
JSON.{dump,generate} offered by the JSON gem is not compatiable with Rails at the moment and can cause a lot of subtle bugs when passed certain data structures. This changed all direct usage of the JSON gem in internal Rails code to always go through AS::JSON.{decode,encode}. We also shouldn't be implementing `to_json` most of the time, and these occurances are replaced with an equivilent `as_json` implementation to avoid problems down the road. See [1] for all the juicy details. [1]: intridea/multi_json#138 (comment)
-
- 19 9月, 2013 1 次提交
-
-
由 kennyj 提交于
-
- 01 4月, 2013 1 次提交
-
-
由 Vipul A M 提交于
-
- 25 3月, 2013 1 次提交
-
-
由 Jeremy Kemper 提交于
* Fix named route collision in mount test fixture * Update controller named route precedence test
-
- 27 2月, 2013 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 03 1月, 2013 1 次提交
-
-
由 Yves Senn 提交于
-
- 28 8月, 2012 1 次提交
-
-
由 schneems 提交于
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
-
- 20 8月, 2012 1 次提交
-
-
由 tomykaira 提交于
-
- 15 6月, 2012 2 次提交
-
-
由 kennyj 提交于
-
由 Aaron Patterson 提交于
-
- 05 5月, 2012 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
This fixes the following scenario: resources :contacts do post 'new', action: 'new', on: :collection, as: :new end Where the /new path is not generated because it's considered a canonical action, part of the normal resource actions: new_contacts POST /contacts(.:format) contacts#new Fixes #2999
-
- 02 5月, 2012 1 次提交
-
-
由 Bogdan Gusiev 提交于
-
- 25 4月, 2012 1 次提交
-
-
由 Jose and Yehuda 提交于
In the current router DSL, using the +match+ DSL method will match all verbs for the path to the specified endpoint. In the vast majority of cases, people are currently using +match+ when they actually mean +get+. This introduces security implications. This commit disallows calling +match+ without an HTTP verb constraint by default. To explicitly match all verbs, this commit also adds a :via => :all option to +match+. Closes #5964
-
- 04 3月, 2012 1 次提交
-
-
由 Brian Cardarella 提交于
Allow the root route helper to accept just a string
-
- 02 3月, 2012 1 次提交
-
-
- 26 2月, 2012 1 次提交
-
-
由 Andrew White 提交于
-
- 23 2月, 2012 1 次提交
-
-
由 David Lee 提交于
PATCH is the correct HTML verb to map to the #update action. The semantics for PATCH allows for partial updates, whereas PUT requires a complete replacement. Changes: * adds config.default_method_for_update you can set to :patch * optionally use PATCH instead of PUT in resource routes and forms * adds the #patch verb to routes to detect PATCH requests * adds #patch? to Request * changes documentation and comments to indicate support for PATCH This change maintains complete backwards compatibility by keeping :put as the default for config.default_method_for_update.
-
- 15 2月, 2012 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 12 2月, 2012 1 次提交
-
-
由 Thiago Pradi 提交于
-
- 24 1月, 2012 2 次提交
-
-
由 Aaron Patterson 提交于
symbol nodes. Fixes #4585
-
由 Aaron Patterson 提交于
-
- 17 1月, 2012 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
- 06 1月, 2012 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 25 12月, 2011 1 次提交
-
-
由 Sergey Nartimov 提交于
-
- 23 12月, 2011 2 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 22 12月, 2011 2 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 23 12月, 2011 2 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 20 12月, 2011 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 05 12月, 2011 1 次提交
-
-
由 Andy Jeffries 提交于
Named Routes shouldn't override existing ones (currently route recognition goes with the earliest match, named routes use the latest match)
-
- 30 11月, 2011 1 次提交
-
-
由 lest 提交于
-
- 28 11月, 2011 1 次提交
-
-
由 karevn 提交于
-
- 17 8月, 2011 1 次提交
-
-
由 Trek Glowacki 提交于
When a route references a missing controller, raise ActionController::RoutingError with a clearer message
-
- 14 8月, 2011 1 次提交
-
-
由 Vishnu Atrai 提交于
-
- 13 8月, 2011 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 01 8月, 2011 1 次提交
-
-
由 Vishnu Atrai 提交于
-
- 03 5月, 2011 1 次提交
-
-
由 Josh Kalderimis 提交于
raise an error if the old router draw method is used, along with a message advising them to either upgrade their routes or add rails_legacy_mapper to their Gemfile
-