- 02 9月, 2011 1 次提交
-
-
由 Carlos Paramio 提交于
-
- 14 8月, 2011 7 次提交
-
-
由 Franck Verrot 提交于
-
由 thedarkone 提交于
-
由 thedarkone 提交于
This fixes a bug that is caused by Resource/SingletonResource mangling resource options when using inline "multi"-resource declarations.
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Erik Michaels-Ober 提交于
When format is true, it is mandatory (as opposed to :format => false). This is currently not possible with resource routes, which automatically make format optional by default.
-
- 29 7月, 2011 2 次提交
-
-
由 thedarkone 提交于
-
由 thedarkone 提交于
This fixes a bug that is caused by Resource/SingletonResource mangling resource options when using inline "multi"-resource declarations.
-
- 28 7月, 2011 1 次提交
-
-
由 Franck Verrot 提交于
-
- 27 7月, 2011 3 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 26 7月, 2011 2 次提交
-
-
由 Erik Michaels-Ober 提交于
When format is true, it is mandatory (as opposed to :format => false). This is currently not possible with resource routes, which automatically make format optional by default.
-
由 Dave Rogers 提交于
addresses issue #1907 - any routes that follow a route with a constraints block are inheriting the previous route's constraints.
-
- 16 7月, 2011 1 次提交
-
-
由 Hendy Tanata 提交于
Previously it was: {:controller=>"photos", :action=>"show", :id=>/[A-Z]\d{5}/} Now it becomes: photos#show {:id=>/[A-Z]\d{5}/}
-
- 15 6月, 2011 1 次提交
-
-
由 bagwanpankaj 提交于
-
- 10 6月, 2011 2 次提交
- 07 6月, 2011 1 次提交
-
-
由 Raghunadh 提交于
-
- 01 6月, 2011 1 次提交
-
-
由 Damien Mathieu 提交于
-
- 24 5月, 2011 1 次提交
-
-
由 Sebastian Martinez 提交于
-
- 22 5月, 2011 1 次提交
-
-
由 Anuj Dutta 提交于
-
- 21 5月, 2011 1 次提交
-
-
由 Andrew White 提交于
-
- 20 5月, 2011 1 次提交
-
-
由 Diego Plentz 提交于
-
- 14 5月, 2011 1 次提交
-
-
由 Xavier Noria 提交于
-
- 10 5月, 2011 2 次提交
-
-
由 James Miller 提交于
-
由 Sebastian Martinez 提交于
-
- 06 5月, 2011 1 次提交
-
-
Update the description of the :path option to #resources to reflect that it sets the actual path, not a prefix. Most instances were already fixed.
-
- 13 4月, 2011 1 次提交
-
-
由 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?`.
-
- 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?.
-
- 29 3月, 2011 1 次提交
-
-
由 Prem Sichanugrist 提交于
Update the wildcard route to be non-greedy by default, therefore be able to match the (.:format) segment [#6605 state:resolved] After some discussion with Andrew White, it seems like this is a better approach for handling a wildcard route. However, user can still bring back the old behavior by supplying `:format => false` to the route. Signed-off-by: NAndrew White <andyw@pixeltrix.co.uk>
-
- 23 3月, 2011 1 次提交
-
-
由 Prem Sichanugrist 提交于
This will make the output of `rake routes` to be correctly match to the behavior of the application, as the regular expression used to match the path is greedy and won't capture the format part by default
-
- 15 3月, 2011 3 次提交
-
-
由 Gabriel Horner 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 12 3月, 2011 2 次提交
-
-
由 Aaron Patterson 提交于
indirection. clever--
-
由 Aaron Patterson 提交于
-