- 02 12月, 2012 2 次提交
-
-
由 Florent Guilleux 提交于
This reverts commit 90c887fa.
-
由 Florent Guilleux 提交于
-
- 28 10月, 2012 1 次提交
-
-
由 AvnerCohen 提交于
-
- 27 10月, 2012 1 次提交
-
-
由 Yves Senn 提交于
-
- 06 8月, 2012 1 次提交
-
-
由 Xavier Noria 提交于
Selecting which key extensions to include in active_support/rails made apparent the systematic usage of Object#in? in the code base. After some discussion in https://github.com/rails/rails/commit/5ea6b0df9a36d033f21b52049426257a4637028d we decided to remove it and use plain Ruby, which seems enough for this particular idiom. In this commit the refactor has been made case by case. Sometimes include? is the natural alternative, others a simple || is the way you actually spell the condition in your head, others a case statement seems more appropriate. I have chosen the one I liked the most in each case.
-
- 03 8月, 2012 2 次提交
-
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
-
- 21 7月, 2012 1 次提交
-
-
由 Xavier Noria 提交于
-
- 19 7月, 2012 1 次提交
-
-
由 Shigeya Suzuki 提交于
- #respond_to's documentation refer to .respond_to, but it was written as just <respond_to>. Added class name for clarification.
-
- 24 5月, 2012 1 次提交
-
- 20 5月, 2012 1 次提交
-
-
由 Henrik Hodne 提交于
For future reference, this is the regex I used: ^\s*#\s*\n(?!\s*#). Replace with the first match, and voilà! Note that the regex matches a little bit too much, so you probably want to `git add -i .` and go through every single diff to check if it actually should be changed.
-
- 15 5月, 2012 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 06 5月, 2012 2 次提交
-
-
由 Steven Soroka 提交于
-
由 Steven Soroka 提交于
Raise a rescuable exception when Rails doesn't know what to do with the format, rather than responding with a head :not_acceptable (406)
-
- 03 4月, 2012 1 次提交
-
-
由 Alexey Vakhov 提交于
-
- 18 3月, 2012 3 次提交
-
-
由 Mark Thomson 提交于
-
由 Mark Thomson 提交于
-
由 Mark Thomson 提交于
-
- 13 3月, 2012 2 次提交
-
-
由 Mark Thomson 提交于
-
由 Mark Thomson 提交于
-
- 07 3月, 2012 2 次提交
-
-
由 José Valim 提交于
-
由 Santiago Pastorino 提交于
-
- 06 3月, 2012 1 次提交
-
-
由 Prem Sichanugrist 提交于
We should let the responder to decide what to do with the given overridden response block, and not short circuit it. Fixes #5280
-
- 04 3月, 2012 1 次提交
-
-
由 Vishnu Atrai 提交于
-
- 22 2月, 2012 1 次提交
-
-
由 Santiago Pastorino 提交于
Closes #5025 part 2
-
- 04 2月, 2012 2 次提交
-
-
由 José Valim 提交于
-
由 Prem Sichanugrist 提交于
Default responder was only using the given respond block when user requested for HTML format, or JSON/XML format with valid resource. This fix the responder so that it will use the given block regardless of the validity of the resource. Note that in this case you'll have to check for object's validity by yourself in the controller. Fixes #4796
-
- 07 11月, 2011 1 次提交
-
-
由 Vijay Dev 提交于
-
- 11 10月, 2011 1 次提交
-
-
由 Alexey Vakhov 提交于
-
- 18 4月, 2011 1 次提交
-
-
由 José Valim 提交于
-
- 13 4月, 2011 1 次提交
-
-
由 Xavier Noria 提交于
-
- 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?.
-
- 10 4月, 2011 1 次提交
-
-
由 Jo Liss 提交于
So we don't miss out on the nice documentation of the respond_to and respond_with instance methods. Also added :nodoc: to protected method.
-
- 01 4月, 2011 1 次提交
-
-
由 Josh Kalderimis 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 31 3月, 2011 1 次提交
-
-
由 Amaia Castro 提交于
Explain in the method doc that you need to call respond_to at the class level in order to use respond_with.
-
- 19 12月, 2010 2 次提交
- 26 11月, 2010 3 次提交
-
-
由 Santiago Pastorino 提交于
-
由 Josh Kalderimis 提交于
Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>
-
由 Josh Kalderimis 提交于
-