- 30 6月, 2010 17 次提交
-
-
由 Santiago Pastorino 提交于
We are trying to test that & escapes here not that & is being escaped, also added a cosmetic change to test_link_tag_with_query_and_no_name Signed-off-by: NJeremy Kemper <jeremy@bitsweat.net>
-
由 Gonçalo Silva 提交于
-
由 Aaron Patterson 提交于
Signed-off-by: NJeremy Kemper <jeremy@bitsweat.net>
-
由 Tekin 提交于
Signed-off-by: NXavier Noria <fxn@hashref.com>
-
由 Xavier Noria 提交于
s/escape_once/html_escape/, since html safety is the contract that now says whether something has to be escaped
-
由 Xavier Noria 提交于
Rationale: url_for is just a path/URL generator, it is the responsability of the caller to escape conveniently HTML needs it, JavaScript needs different escaping, a text mail needs no escaping at all, etc.
-
由 José Valim 提交于
-
由 wycats 提交于
-
由 wycats 提交于
-
由 wycats 提交于
Create a deprecation behavior that triggers a notification for deprecation notices, and make the behaviors independent of the environment names. * In Rails 2.3 apps being upgraded, you will need to add the deprecation configuration to each of your environments. Failing to do so will result in the same behavior as Rails 2.3, but with an outputted warning to provide information on how to set up the setting. * New Rails 3 applications generate the setting * The notification style will send deprecation notices using ActiveSupport::Notifications. Third-party tools can listen in to these notifications to provide a streamlined view of the deprecation notices occurring in your app. * The payload in the notification is the deprecation warning itself as well as the callstack from the point that triggered the notification.
-
由 J. Pablo Fernández 提交于
[#4809 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Paul Barry 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 J. Pablo Fernández 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
No need to check if the attribute exists (this is the same behavior as in 2.3) [#4994 state:resolved] and [#5003 state:resolved]
-
由 José Valim 提交于
-
由 Jeremy Kemper 提交于
Revert "Revert "Name compiled render methods". This caused several failures on AP test suite for 1.9.2." This reverts commit 9013227e. minitest was 'running' compiled templates beginning with test!
-
由 José Valim 提交于
-
- 29 6月, 2010 15 次提交
-
-
由 Neeraj Singh 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Neeraj Singh 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 David Trasbo 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 José Valim 提交于
Add scoping and unscoped as the syntax to replace the old with_scope and with_exclusive_scope. A few examples: * with_scope now should be scoping: Before: Comment.with_scope(:find => { :conditions => { :post_id => 1 } }) do Comment.first #=> SELECT * FROM comments WHERE post_id = 1 end After: Comment.where(:post_id => 1).scoping do Comment.first #=> SELECT * FROM comments WHERE post_id = 1 end * with_exclusive_scope now should be unscoped: class Post < ActiveRecord::Base default_scope :published => true end Post.all #=> SELECT * FROM posts WHERE published = true Before: Post.with_exclusive_scope do Post.all #=> SELECT * FROM posts end After: Post.unscoped do Post.all #=> SELECT * FROM posts end Notice you can also use unscoped without a block and it will return an anonymous scope with default_scope values: Post.unscoped.all #=> SELECT * FROM posts
-
由 José Valim 提交于
This reverts commit 2c4f8aae.
-
由 Santiago Pastorino 提交于
-
由 Neeraj Singh 提交于
with_exclusive_scope does not work properly if ARel is passed. It does work nicely if hash is passed. Blow up if user is attempting it pass ARel to with_exclusive_scope. [#3838 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
-
由 Santiago Pastorino 提交于
[#4942 state:committed] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Leigh Caplan 提交于
[#4942] Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com> Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 28 6月, 2010 8 次提交
-
-
由 José Valim 提交于
-
由 José Valim 提交于
-
由 Andrew White 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 Andrew White 提交于
HTML specifications recommend the escaping of urls in web pages, which url_for does by default for string urls and consquently urls generated by path helpers as these return strings. Hashes passed to url_for are not escaped by default and this commit reverses this default so that they are escaped. Undoes the changes of this commit: http://github.com/rails/rails/commit/1b3195b63ca44f0a70b61b75fcf4991cb2fbb944Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Andrew White 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 rohit 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Andrew White 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-