- 13 4月, 2011 2 次提交
-
-
由 Prem Sichanugrist 提交于
After a long list of discussion about the performance problem from using varargs and the reason that we can't find a great pair for it, it would be best to remove support for it for now. It will come back if we can find a good pair for it. For now, Bon Voyage, `#among?`.
-
由 Xavier Noria 提交于
-
- 12 4月, 2011 1 次提交
-
-
由 David Heinemeier Hansson 提交于
-
- 11 4月, 2011 1 次提交
-
-
由 Prem Sichanugrist 提交于
There're a lot of places in Rails source code which make a lot of sense to switching to Object#in? or Object#either? instead of using [].include?.
-
- 01 4月, 2011 3 次提交
-
-
由 Josh Kalderimis 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Josh Kalderimis 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Josh Kalderimis 提交于
when using respond_with with an invalid resource and custom options, the default response status and error messages should be returned Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 18 1月, 2011 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 27 12月, 2010 1 次提交
-
-
由 wycats 提交于
-
- 28 11月, 2010 1 次提交
-
-
由 José Valim 提交于
-
- 25 11月, 2010 3 次提交
-
-
由 Neeraj Singh 提交于
If a user wants json output then try best to render json output. In such cases prefer kind_of(String) over respond_to?(to_str) [#5841 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Neeraj Singh 提交于
-
由 Neeraj Singh 提交于
-
- 23 11月, 2010 4 次提交
-
-
由 Neeraj Singh 提交于
it could be cleaned up on teardown. Currently the test code test/controller/mime_responds_test.rb impacts test/dispatch/mime_type_test.rb. dispatch/mime_type_test.rb runs independently fine but when run as part of rake breaks because of new mime types registered in controller/mime_responds_test.rb Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Neeraj Singh 提交于
leading */* and comma Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Neeraj Singh 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Neeraj Singh 提交于
has ....,*/* . It is possible to a device to send request such that */* appear at the beginning of the "Accept" header. This patch ensures that "Accept" header is ignored for such cases too. Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 06 11月, 2010 1 次提交
-
-
由 Chris Eppstein 提交于
Correctly handle the case of an API response that returns a hash by treating a single hash argument as the resource instead of as options.
-
- 12 10月, 2010 1 次提交
-
-
由 Szymon Nowak 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 27 9月, 2010 1 次提交
-
-
由 Emilio Tagua 提交于
-
- 05 9月, 2010 1 次提交
-
-
由 Piotr Sarnacki 提交于
-
- 14 8月, 2010 2 次提交
-
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
- 05 7月, 2010 1 次提交
-
-
由 Patrik Stenmark 提交于
Signed-off-by: Nwycats <wycats@gmail.com>
-
- 24 5月, 2010 1 次提交
-
-
由 José Valim 提交于
-
- 17 4月, 2010 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 20 3月, 2010 1 次提交
-
-
由 wycats 提交于
-
- 04 3月, 2010 1 次提交
-
-
由 Carl Lerche 提交于
-
- 21 2月, 2010 1 次提交
-
-
由 José Valim 提交于
Require persisted? in ActiveModel::Lint and remove new_record? and destroyed? methods. ActionPack does not care if the resource is new or if it was destroyed, it cares only if it's persisted somewhere or not.
-
- 31 1月, 2010 1 次提交
-
-
由 José Valim 提交于
-
- 11 1月, 2010 1 次提交
-
-
由 José Valim 提交于
-
- 09 12月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
-
- 08 12月, 2009 1 次提交
-
-
由 José Valim 提交于
Signed-off-by: NYehuda Katz <wycats@Yehuda-Katz.local>
-
- 02 12月, 2009 1 次提交
-
-
由 José Valim 提交于
Signed-off-by: NYehuda Katz <wycats@Yehuda-Katz.local>
-
- 14 11月, 2009 1 次提交
-
-
由 José Valim 提交于
Signed-off-by: NJeremy Kemper <jeremy@bitsweat.net>
-
- 17 10月, 2009 1 次提交
-
-
由 José Valim 提交于
Unify class_inheritable_accessor and extlib_inheritable_accessor and allow responder to be set in the class level.
-
- 04 10月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
-
- 30 8月, 2009 1 次提交
-
-
由 José Valim 提交于
-
- 17 8月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
Cleanup route reloading in tests. Prefer with_routing over using ActionController::Routing::Routes directly
-
- 16 8月, 2009 1 次提交
-
-
由 Yehuda Katz 提交于
* request.formats is much simpler now * For XHRs or Accept headers with a single item, we use the Accept header * For other requests, we use params[:format] or fallback to HTML * This is primarily to work around the fact that browsers provide completely broken Accept headers, so we have to whitelist the few cases we can specifically isolate and treat other requests as coming from the browser * For APIs, we can support single-item Accept headers, which disambiguates from the browsers * Requests to an action that only has an XML template from the browser will no longer find the template. This worked previously because most browsers provide a catch-all */*, but this was mostly accidental behavior. If you want to serve XML, either use the :xml format in links, or explicitly specify the XML template: render "template.xml".
-