1. 14 12月, 2019 1 次提交
  2. 10 12月, 2019 1 次提交
  3. 27 11月, 2019 1 次提交
  4. 13 11月, 2019 2 次提交
  5. 05 11月, 2019 1 次提交
  6. 01 11月, 2019 1 次提交
  7. 17 8月, 2019 1 次提交
  8. 05 8月, 2019 1 次提交
  9. 23 7月, 2019 1 次提交
  10. 28 5月, 2019 1 次提交
  11. 25 4月, 2019 2 次提交
  12. 20 4月, 2019 1 次提交
  13. 04 4月, 2019 1 次提交
  14. 02 4月, 2019 2 次提交
  15. 31 3月, 2019 1 次提交
  16. 23 3月, 2019 2 次提交
  17. 11 3月, 2019 1 次提交
    • E
      Prep release · 7c87fd56
      eileencodes 提交于
      * Update RAILS_VERSION
      * Bundle
      * rake update_versions
      * rake changelog:header
      7c87fd56
  18. 26 2月, 2019 1 次提交
  19. 07 2月, 2019 2 次提交
  20. 28 1月, 2019 1 次提交
  21. 26 1月, 2019 1 次提交
  22. 19 1月, 2019 2 次提交
  23. 18 1月, 2019 1 次提交
  24. 27 12月, 2018 1 次提交
    • G
      Don't expect defined protect_against_forgery? in {token,csrf_meta}_tag · a58db74c
      Genadi Samokovarov 提交于
      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.
      a58db74c
  25. 20 12月, 2018 1 次提交
  26. 06 12月, 2018 1 次提交
  27. 05 12月, 2018 1 次提交
  28. 20 11月, 2018 1 次提交
  29. 08 11月, 2018 1 次提交
  30. 10 10月, 2018 1 次提交
    • E
      Add allocations to template renderer subscription · e8c1be4a
      Eileen Uchitelle 提交于
      This PR adds the allocations to the instrumentation for template and
      partial rendering.
      
      Before:
      
      ```
        Rendering posts/new.html.erb within layouts/application
        Rendered posts/_form.html.erb (9.7ms)
        Rendered posts/new.html.erb within layouts/application (10.9ms)
      Completed 200 OK in 902ms (Views: 890.8ms | ActiveRecord: 0.8ms)
      ```
      
      After:
      
      ```
        Rendering posts/new.html.erb within layouts/application
        Rendered posts/_form.html.erb (Duration: 7.1ms | Allocations: 6004)
        Rendered posts/new.html.erb within layouts/application (Duration: 8.3ms | Allocations: 6654)
      Completed 200 OK in 858ms (Views: 848.4ms | ActiveRecord: 0.4ms | Allocations: 1539564)
      ```
      e8c1be4a
  31. 02 10月, 2018 1 次提交
    • J
      respect path_only option when an array is passed into url_for · b48c2ade
      Joel Ambass 提交于
      The url_for method is now extracting the path_only option in order to determine if polymorphic_path or polymorphic_url should be called.
      
      If the path_only option is not set it will be set to true unless the host option is set. This behaviour is the same as when a Hash or Params object is passed.
      
      To support this unifying the code responsible for setting this default value has been extracted into a private method
      b48c2ade
  32. 07 9月, 2018 1 次提交
  33. 08 8月, 2018 2 次提交