1. 19 10月, 2012 1 次提交
  2. 16 10月, 2012 1 次提交
  3. 15 10月, 2012 1 次提交
  4. 11 10月, 2012 1 次提交
  5. 10 10月, 2012 1 次提交
    • M
      Update test locations · 2a68f68a
      Mike Moore 提交于
      Change the default test locations to avoid confusion around the common
      testing terms "unit" and "functional".
      Add new rake tasks for the new locations, while maintaining backwards
      compatibility with the old rake tasks.
      
      New testing locations are as follows:
      
          app/models -> test/models (was test/units)
          app/helpers -> test/helpers (was test/units/helpers)
          app/controllers -> test/controllers (was test/functional)
          app/mailers -> test/mailers (was test/functional)
      2a68f68a
  6. 02 10月, 2012 1 次提交
  7. 22 9月, 2012 1 次提交
  8. 17 9月, 2012 2 次提交
  9. 13 9月, 2012 1 次提交
    • D
      change app/plugin generators to be more SCM agnostic · ceb05bd1
      Derek Prior 提交于
      Users of other SCM's can now generate rails
      apps that will add the "empty" directories to source control,
      but will not have a useless .gitignore or mis-named .gitkeep
      files.
      
      * Change `rails new` and `rails plugin new` generators to name
        the `.gitkeep` as `.keep` in a more SCM-agnostic way.
      
      * Change `--skip-git` option to only skip the `.gitignore` file
        and still generate the `.keep` files.
      
      * Add `--skip-keeps` option to skip the `.keep` files.
      
      It closes #2800.
      ceb05bd1
  10. 11 8月, 2012 2 次提交
    • J
      09d2671c
    • J
      Remove the dependent_restrict_raises option. · 5ad79989
      Jon Leighton 提交于
      It's not really a good idea to have this as a global config option. We
      should allow people to specify the behaviour per association.
      
      There will now be two new values:
      
      * :dependent => :restrict_with_exception implements the current
        behaviour of :restrict. :restrict itself is deprecated in favour of
        :restrict_with_exception.
      * :dependent => :restrict_with_error implements the new behaviour - it
        adds an error to the owner if there are dependent records present
      
      See #4727 for the original discussion of this.
      5ad79989
  11. 08 8月, 2012 1 次提交
  12. 31 5月, 2012 1 次提交
  13. 14 5月, 2012 3 次提交
  14. 08 5月, 2012 1 次提交
  15. 02 5月, 2012 1 次提交
  16. 17 4月, 2012 1 次提交
  17. 10 4月, 2012 1 次提交
  18. 02 4月, 2012 1 次提交
    • P
      Usage file in generators shouldn't be fetched only based on source_root · fff3e75e
      Piotr Sarnacki 提交于
      In case `source_roout` is not set, `default_source_root` is used,
      which includes also `templates` directory. If there is no `templates`
      directory, `default_source_root` is not available and USAGE will not
      be displayed. USAGE should be also checked based on default
      directory excluding `templates`.
      fff3e75e
  19. 21 3月, 2012 1 次提交
  20. 18 3月, 2012 1 次提交
  21. 15 3月, 2012 1 次提交
  22. 14 3月, 2012 6 次提交
  23. 05 3月, 2012 1 次提交
  24. 25 2月, 2012 1 次提交
  25. 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
  26. 01 2月, 2012 1 次提交
  27. 31 1月, 2012 1 次提交
  28. 29 1月, 2012 1 次提交
  29. 13 1月, 2012 1 次提交
  30. 03 1月, 2012 1 次提交
  31. 21 12月, 2011 1 次提交