- 04 9月, 2010 30 次提交
-
-
由 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 提交于
-
由 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 提交于
Refactored tests for prefix generation and added test for url generation in regular class with default_url_options[:script_name] set
-
由 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 提交于
I added integration tests for generating urls in Engine and application and tweaked Engines to fully cooparate with new router's behavior: * Rails.application now sets ORIGINAL_SCRIPT_NAME * Rails.application also sets its routes as env['action_dispatch.parent_routes'] * Engine implements responds_to? class method to respond to all the instance methods, like #routes
-
由 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 提交于
Pass routes via env['action_dispatch.routes'], it's needed by routes to determine if it should generate prefix for mounted apps
-
由 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 提交于
Move singleton pattern to Railtie and remove Engine::Configurable and Application::Configurable in favor of unified Railtie::Configurable
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
We don't need to add railties initlaizers in Application as there is already done in Engine and it's called with super
-
由 Piotr Sarnacki 提交于
Removed ActionDispatch::Static, but left empty MiddlewareStack to unify app method between Engine and Application
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
-
由 Xavier Noria 提交于
too many people are looking for the 2.3 guides, put by now a link at the top of the home, and add the Rails version in the main header
-
由 Xavier Noria 提交于
-
- 03 9月, 2010 2 次提交
-
-
由 Ken Collins 提交于
Signed-off-by: NMichael Koziarski <michael@koziarski.com>
-
由 José Valim 提交于
Booting a new Rails application does not work after this commit [#5359 state:open] This reverts commit 38a421b3.
-
- 02 9月, 2010 8 次提交
-
-
由 rohit 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 rohit 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 rohit 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Andreas Garnæs 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 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>
-