1. 27 7月, 2012 1 次提交
  2. 24 5月, 2012 1 次提交
    • V
      Revert "Remove blank trailing comments" · 1ad0b378
      Vijay Dev 提交于
      This reverts commit fa6d921e.
      
      Reason: Not a fan of such massive changes. We usually close such changes
      if made to Rails master as a pull request. Following the same principle
      here and reverting.
      
      [ci skip]
      1ad0b378
  3. 20 5月, 2012 1 次提交
    • H
      Remove blank trailing comments · fa6d921e
      Henrik Hodne 提交于
      For future reference, this is the regex I used: ^\s*#\s*\n(?!\s*#). Replace
      with the first match, and voilà! Note that the regex matches a little bit too
      much, so you probably want to `git add -i .` and go through every single diff
      to check if it actually should be changed.
      fa6d921e
  4. 15 5月, 2012 1 次提交
  5. 03 5月, 2012 1 次提交
  6. 09 4月, 2012 1 次提交
  7. 06 4月, 2012 1 次提交
  8. 05 4月, 2012 2 次提交
  9. 02 3月, 2012 2 次提交
  10. 04 1月, 2012 1 次提交
  11. 30 12月, 2011 1 次提交
  12. 09 12月, 2011 1 次提交
  13. 25 11月, 2011 2 次提交
  14. 04 10月, 2011 1 次提交
  15. 28 8月, 2011 1 次提交
  16. 12 8月, 2011 2 次提交
  17. 24 5月, 2011 1 次提交
  18. 11 5月, 2011 1 次提交
  19. 24 11月, 2010 1 次提交
  20. 23 11月, 2010 1 次提交
  21. 29 9月, 2010 2 次提交
  22. 28 9月, 2010 1 次提交
  23. 27 9月, 2010 1 次提交
  24. 04 9月, 2010 7 次提交
    • P
      f3c703a3
    • P
      Add mounted_helpers to routes · 6c95e0f8
      Piotr Sarnacki 提交于
      mounted_helpers are a bit similar to url_helpers. They're automatically
      included in controllers for Rails.application and each of mounted
      Engines. Mounted helper allows to call url_for and named helpers for
      given application.
      
      Given Blog::Engine mounted as blog_engine, there are 2 helpers defined:
      app and blog_engine. You can call routes for app and engine using those
      helpers:
      
      app.root_url
      app.url_for(:controller => "foo")
      blog_engine.posts_path
      blog_engine.url_for(@post)
      6c95e0f8
    • P
      Routes refactoring: · e9791bec
      Piotr Sarnacki 提交于
      * added more tests for prefix generation
      * fixed bug with generating host for both prefix and url
      * refactored url_for method
      * organized tests for prefix generation
      e9791bec
    • P
      Extended url_for to handle specifying which router should be used. · b53efd21
      Piotr Sarnacki 提交于
      A few examples:
      url_for Blog::Engine, :posts_path
      url_for Blog::Engine, @post
      url_for Blog::Engine, :action => "main", :controller => "index"
      b53efd21
    • P
      New way of generating urls for Application from Engine. · eedbf87d
      Piotr Sarnacki 提交于
      It's based specifying application's script_name with:
      Rails.application.default_url_options = {:script_name => "/foo"}
      
      default_url_options method is delegated to routes. If router
      used to generate url differs from the router passed via env
      it always overwrites :script_name with this value.
      eedbf87d
    • P
      Allow to generate Application routes inside Engine · 451c9942
      Piotr Sarnacki 提交于
      This requires knowledge about original SCRIPT_NAME and
      the parent router. It should be pass through the env
      as ORIGIAL_SCRIPT_NAME and action_dispatch.parent_routes
      451c9942
    • P
      Use env['action_dispatch.routes'] to determine if we should generate prefix or not. · 28016d33
      Piotr Sarnacki 提交于
      This technique is here to allow using routes from Engine in Application
      and vice versa. When using Engine routes inside Application it should
      generate prefix based on mount point. When using Engine routes inside
      Engine it should use env['SCRIPT_NAME']. In any other case it should
      generate prefix as env should not be even available.
      28016d33
  25. 29 8月, 2010 1 次提交
  26. 30 7月, 2010 1 次提交
  27. 22 7月, 2010 1 次提交
  28. 21 7月, 2010 1 次提交
  29. 02 7月, 2010 1 次提交