- 04 9月, 2010 33 次提交
-
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
Add possibility to explicitly call engine's routes through polymorphic_routes, for example: polymorphic_url([blog, @post])
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
Set only helpers_path on inherited hook in action_controller/railtie.rb and use helper(:all) just after that
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
This change is needed, because we must take namespace into account and if controller's/mailer's class is namespaced, engine's paths should be set instead of application's ones. The nice side effect of this is removing unneeded logic in ActionController::Base.inherited - now the helpers_path should be set correctly even for engine's controllers, so helper(:all) will always include correct helpers.
-
由 Piotr Sarnacki 提交于
This change allows using namespaced models with polymorphic_url, in the way that you would use them without namespace. Let's say that you have Blog::Post model in namespaced Engine. When you use polymorphic_path with Blog::Post instances, like in form_for(@post), it will look for blog_posts_path named url helper. As we are inside Blog::Engine, it's annoying to always use the prefix. With this commit, blog_ prefix will be removed and posts_path will be called.
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
Move ActionController::Railties::RoutesHelpers and ActionMailer::Railties::RoutesHelper to AbstractController::Railties::RoutesHelpers
-
由 Piotr Sarnacki 提交于
There were actually 2 problems with this one: * script_name was added to options as a string and then it was used in RouteSet#url_for with usage of <<, which was changing the original script_name * the second issue was with _with_routes method. It was called in RoutesProxy to modify _routes in view_context, but url_helpers in views is just delegating it to controller, so another _with_routes call is needed there
-
由 Piotr Sarnacki 提交于
Include application's helpers and router helpers by default, but include engine's ones for controllers inside isolated namespace
-
由 Piotr Sarnacki 提交于
For view_context we need to initialize RoutesProxy in context of controller, not view, quick fix, I need to dig into it later
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 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)
-
由 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
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
A few examples: url_for Blog::Engine, :posts_path url_for Blog::Engine, @post url_for Blog::Engine, :action => "main", :controller => "index"
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 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.
-
由 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
-
由 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.
-
由 Piotr Sarnacki 提交于
-
- 03 9月, 2010 1 次提交
-
-
由 José Valim 提交于
Booting a new Rails application does not work after this commit [#5359 state:open] This reverts commit 38a421b3.
-
- 02 9月, 2010 4 次提交
-
-
由 José Valim 提交于
Ensure routes are loaded only after the initialization process finishes, ensuring all configuration options were applied.
-
由 Łukasz Strzałkowski 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Łukasz Strzałkowski 提交于
Now it's more transparent, and readable Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Thiago Pradi 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 01 9月, 2010 2 次提交
-
-
由 Andrew White 提交于
Move implicit nested call before options handling so that nested constraints work [#5513 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Alex Chrome 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-