1. 07 3月, 2012 1 次提交
  2. 06 3月, 2012 1 次提交
  3. 03 3月, 2012 3 次提交
  4. 23 2月, 2012 1 次提交
    • D
      Add config.default_method_for_update to support PATCH · 002713c6
      David Lee 提交于
      PATCH is the correct HTML verb to map to the #update action. The
      semantics for PATCH allows for partial updates, whereas PUT requires a
      complete replacement.
      
      Changes:
      * adds config.default_method_for_update you can set to :patch
      * optionally use PATCH instead of PUT in resource routes and forms
      * adds the #patch verb to routes to detect PATCH requests
      * adds #patch? to Request
      * changes documentation and comments to indicate support for PATCH
      
      This change maintains complete backwards compatibility by keeping :put
      as the default for config.default_method_for_update.
      002713c6
  5. 22 2月, 2012 2 次提交
  6. 20 2月, 2012 1 次提交
  7. 15 2月, 2012 1 次提交
    • F
      Fix sanitize_for_mass_assigment when role is nil · d204918f
      Fabio Yamate 提交于
      There is an example in Rails documentation that suggests implementing
      assign_attributes method for ActiveModel interface, that by default
      sends option role with nil. Since mass_assignment_authorizer never
      is called without args, we can move the default value internally.
      d204918f
  8. 14 2月, 2012 1 次提交
  9. 13 2月, 2012 1 次提交
  10. 12 2月, 2012 2 次提交
  11. 08 2月, 2012 2 次提交
  12. 06 2月, 2012 1 次提交
    • N
      To infinity… and beyond! · 60dad828
      Niels Ganser 提交于
      Allow infinite values for validates_length_of. Particularly useful
      for prettily defining an open ended range such as
      
      validates_length_of :human_stupidity, :within => 0..Float::INFINITY
      60dad828
  13. 03 2月, 2012 1 次提交
  14. 02 2月, 2012 1 次提交
  15. 01 2月, 2012 1 次提交
  16. 27 1月, 2012 1 次提交
  17. 25 1月, 2012 2 次提交
  18. 20 1月, 2012 1 次提交
  19. 17 1月, 2012 5 次提交
  20. 15 1月, 2012 1 次提交
    • P
      Fix stack level too deep when model does not have attributes method. · b164e81c
      Piotr Sarnacki 提交于
      Without that patch when using ActiveModel::AttributeMethods
      in a class that does not respond to `attributes` method,
      stack level too deep error will be raised on non existing
      method. While documentation is clear that you need to define
      `attributes` method in order to use AttributeMethods module,
      `stack level too deep` is rather obscure and hard to debug,
      therefore we should try to not break `method_missing` if
      someone forgets about defining `attributes`.
      b164e81c
  21. 07 1月, 2012 1 次提交
  22. 06 1月, 2012 4 次提交
  23. 05 1月, 2012 5 次提交