aboutsummaryrefslogtreecommitdiffstats
path: root/actionview/test/template/resolver_patterns_test.rb
diff options
context:
space:
mode:
authorGenadi Samokovarov <gsamokovarov@gmail.com>2018-12-26 21:10:37 +0200
committerGenadi Samokovarov <gsamokovarov@gmail.com>2018-12-27 11:33:54 +0200
commita58db74c4feda7b8e2a02882c030b252d6fa8611 (patch)
treecdb5496cc0faaf4315ef4e5e40304b7fc6b0a7ab /actionview/test/template/resolver_patterns_test.rb
parentb5ed468492387d42a44ca6af525d4a274cda756d (diff)
downloadrails-a58db74c4feda7b8e2a02882c030b252d6fa8611.tar.gz
rails-a58db74c4feda7b8e2a02882c030b252d6fa8611.tar.bz2
rails-a58db74c4feda7b8e2a02882c030b252d6fa8611.zip
Don't expect defined protect_against_forgery? in {token,csrf_meta}_tag
The `#csrf_meta_tags` and `#token_tag` Action View helper methods are expecting the class in which are included to explicitly define the method `#protect_against_forgery?` or else they will fail with `NoMethodError`. This is a problem if you want to use Action View outside of Rails applications. For example, in #34788 I used the `#button_to` helper inside of the error pages templates that have a custom `ActionView::Base` subclass, which did not defined `#protect_against_forgery?` and trying to call the button failed. I had to dig inside of Action View to find-out what's was going on. I think we should either set a default method implementation in the helpers or check for the method definition, but don't explicitly require the presence of `#protect_against_forgery?` in every `ActionViews::Base` subclass as the errors are hard to figure out.
Diffstat (limited to 'actionview/test/template/resolver_patterns_test.rb')
0 files changed, 0 insertions, 0 deletions