1. 30 8月, 2012 3 次提交
  2. 29 8月, 2012 1 次提交
    • X
      CHANGELOGs are now per branch · 810a50da
      Xavier Noria 提交于
      Changes in old branches needed to be manually synched in CHANGELOGs of newer ones.
      This has proven to be brittle, sometimes one just forgets this manual step.
      With this commit we switch to CHANGELOGs per branch. When a new major version is
      cut from master, the CHANGELOGs in master start being blank.
      
      A link to the CHANGELOG of the previous branch allows anyone interested to
      follow the history.
      810a50da
  3. 28 8月, 2012 2 次提交
    • S
      Add Missing Keys from Journey on failed URL format · 0b6175ac
      schneems 提交于
      Many named routes have keys that are required to successfully resolve. If a key is left off like this:
      
          <%= link_to 'user', user_path %>
      
      This will produce an error like this:
      
          No route matches {:action=>"show", :controller=>"users"}
      
      Since we know that the :id is missing, we can add extra debugging information to the error message.
      
          No route matches {:action=>"show", :controller=>"users"} missing required keys: [:id]
      
      
      This will help new and seasoned developers look closer at their parameters. I've also subclassed the routing error to be clear that this error is a result of attempting to generate a url and not because the user is trying to visit a bad url. 
      
      While this may sound trivial this error message is misleading and confuses most developers. The important part isn't what's in the options its's what's missing. Adding this information to the error message will make debugging much more obvious. 
      
      This is the sister pull request of https://github.com/rails/journey/pull/44 which will be required to get they missing keys into the correct error message. 
      
      Example Development Error in Rails: http://cl.ly/image/3S0T0n1T3421
      0b6175ac
    • P
      Update AP's CHANGELOG with user facing changes · daa0ed3a
      Piotr Sarnacki 提交于
      daa0ed3a
  4. 26 8月, 2012 1 次提交
    • V
      correct handling of date selects when using both disabled and discard options · 130fe2b1
      Vasiliy Ermolovich 提交于
      we should take disabled option not only from `html_options` hash but from
      `options` hash too like `build_select` method does it. So
      
      datetime_select("post", "updated_at", { :discard_minute => true }, { :disabled => true })
      datetime_select("post", "updated_at", :discard_minute => true , :disabled => true)
      
      both these variants work now
      
      closes #7431
      130fe2b1
  5. 25 8月, 2012 1 次提交
  6. 22 8月, 2012 1 次提交
  7. 19 8月, 2012 1 次提交
  8. 17 8月, 2012 1 次提交
  9. 15 8月, 2012 1 次提交
  10. 14 8月, 2012 2 次提交
  11. 12 8月, 2012 1 次提交
  12. 11 8月, 2012 2 次提交
  13. 09 8月, 2012 1 次提交
  14. 08 8月, 2012 2 次提交
  15. 07 8月, 2012 2 次提交
  16. 06 8月, 2012 1 次提交
  17. 05 8月, 2012 1 次提交
  18. 04 8月, 2012 1 次提交
  19. 03 8月, 2012 1 次提交
  20. 30 7月, 2012 1 次提交
  21. 24 7月, 2012 1 次提交
  22. 22 7月, 2012 2 次提交
  23. 18 7月, 2012 1 次提交
  24. 09 7月, 2012 1 次提交
  25. 08 7月, 2012 1 次提交
  26. 07 7月, 2012 1 次提交
  27. 03 7月, 2012 1 次提交
  28. 01 7月, 2012 1 次提交
  29. 15 6月, 2012 1 次提交
  30. 12 6月, 2012 1 次提交
  31. 01 6月, 2012 2 次提交