- 29 8月, 2010 1 次提交
-
-
由 Joost Baaij 提交于
Move the default route to the bottom, as this practise should be discouraged. Add documentation for resources, external redirects and Rack applications.
-
- 28 8月, 2010 8 次提交
-
-
由 Joost Baaij 提交于
Worse still, its use breaks some rdoc, replacing method names with a curly brace. Having just one call-seq directive doesn't add anything since this is covered by regular rdoc. Having multiple might make sense, but these are already documented with examples. This partly re-reverts 60de0e56 but does not touch the vendorized code in html-scanner.
-
由 Joost Baaij 提交于
-
由 Xavier Noria 提交于
Revert "call-seq directive makes rdoc cry and replaces method names with a curly brace; besides it doesn't add anything when you only list one call example since this is obviously documented already" Reason: Part of this commit touches vendorized stuff, the rest is fine, could you please repatch? This reverts commit 60de0e56.
-
由 Joost Baaij 提交于
-
由 Joost Baaij 提交于
-
由 Joost Baaij 提交于
-
由 Joost Baaij 提交于
call-seq directive makes rdoc cry and replaces method names with a curly brace; besides it doesn't add anything when you only list one call example since this is obviously documented already
-
由 José Valim 提交于
-
- 27 8月, 2010 13 次提交
-
-
由 Santiago Pastorino 提交于
Make InstanceTagMethods#value_before_type_cast raise if the model don't respond to attr_before_type_cast or attr method [#3374] [#5471 state:committed]
-
由 Carlos Antonio da Silva 提交于
[#5469 state:committed] Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>
-
由 José Valim 提交于
-
由 José Valim 提交于
-
由 Joost Baaij 提交于
-
由 Joost Baaij 提交于
-
由 Joost Baaij 提交于
-
由 Joost Baaij 提交于
-
由 Joost Baaij 提交于
-
由 José Valim 提交于
-
由 José Valim 提交于
-
由 José Valim 提交于
Add clear_helpers as a way to clean up all helpers added to this controller, maintaing just the helper with the same name as the controller.
-
由 José Valim 提交于
-
- 26 8月, 2010 5 次提交
-
-
由 Jaime Iniesta 提交于
Fix capture_helper.rb api documentation, unescaped script tag was breaking it on the content_for explanation
-
由 Jaime Iniesta 提交于
Fix capture_helper.rb api documentation, unescaped script tag was breaking it on the content_for explanation
-
由 Joost Baaij 提交于
This information was lost in commit bd6b61be. This might have been intentional, but this class does represent the starting point for all things related to actions, and as such should document it. I couldn't find any trace of this documentation, which seems like a waste. Updated parts here and there to conform to current best practices.
-
由 Joost Baaij 提交于
-
由 Joost Baaij 提交于
-
- 25 8月, 2010 7 次提交
-
-
由 Rémy Coutable 提交于
-
由 Rémy Coutable 提交于
-
由 Andrew White 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 José Valim 提交于
If you were using symbols before for methods like match/get/post/put/delete, it is likely that this commit will break your routes. Everything should behave the same if you are using strings, if not, please open up a ticket.
-
由 José Valim 提交于
-
由 José Valim 提交于
-
- 24 8月, 2010 6 次提交
-
-
由 Santiago Pastorino 提交于
-
由 Andrew White 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 José Valim 提交于
Fix a bug where symbols and strings were not behaving the same in the router. [#5431 state:resolved]
-
由 Andrew White 提交于
When custom resource actions are specified using strings add the default name and action if the string is a valid ruby method name. [#5431 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 David Heinemeier Hansson 提交于
-