Skip to content
Commits on Oct 3, 2010
  1. @josevalim
Commits on Oct 2, 2010
  1. @josevalim
Commits on Sep 30, 2010
  1. @drogus
  2. @drogus
  3. @drogus

    Properly reload routes defined in class definition

    drogus committed
    Sometimes it's easier to define routes inside Engine or
    Application class definition (e.g. one file applications). The
    problem with such case is that if there is a plugin that
    has config/routes.rb file, it will trigger routes reload on application.
    Since routes definition for application is not in config/routes.rb
    file routes_reloader will fail to reload application's routes
    properly. With this commit you can pass routes definition as a block
    to routes method, which will allow to properly reload it:
    class MyApp::Application < Rails::Application
      routes do
        resources :users
Commits on Sep 15, 2010
  1. Only add Rack::Cache to the middleware stack if config.action_control…

    Sparky committed
    …ler.perform_caching is set.
Commits on Sep 13, 2010
  1. @wycats

    First pass at Rack::Cache

    wycats committed with Carlhuda
Commits on Sep 3, 2010
  1. @drogus

    Get rid of static_paths method and instead configure paths for Action…

    drogus committed
    …Dispatch::Static in initializers
  2. @drogus
  3. @drogus
  4. @drogus
  5. @drogus

    New way of generating urls for Application from Engine.

    drogus committed
    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.
  6. @drogus

    Fix url generation for mounted Engine

    drogus committed
    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
  7. @drogus

    Pass routes via env['action_dispatch.routes'], it's needed by routes …

    drogus committed
    …to determine if it should generate prefix for mounted apps
  8. @drogus

    Move singleton pattern to Railtie and remove Engine::Configurable and…

    drogus committed
    … Application::Configurable in favor of unified Railtie::Configurable
  9. @drogus
  10. @drogus

    We don't need to add railties initlaizers in Application as there is …

    drogus committed
    …already done in Engine and it's called with super
  11. @drogus

    Removed ActionDispatch::Static, but left empty MiddlewareStack to uni…

    drogus committed
    …fy app method between Engine and Application
  12. @drogus
  13. @drogus
Commits on Aug 9, 2010
  1. @wycats
Commits on Jul 28, 2010
  1. @wycats

    Add a header that tells Internet Explorer (all versions) to use the b…

    wycats committed
    …est available standards support. This ensures that IE doesn't go into quirks mode because it has been blacklisted by too many users pressing the incompatible button. It also tells IE to use the ChromeFrame renderer, if the user has installed the plugin.
    This guarantees that the best available standards support will be used on the client.
Commits on Jul 18, 2010
  1. @josevalim

    Add console hook to force ActiveRecord::Base to be loaded when consol…

    josevalim committed
    …e starts avoiding reference loops.
Commits on Jul 2, 2010
  1. @josevalim
Commits on Jul 1, 2010
  1. @josevalim

    Avoid calls to Rails::Application since this is not the official API.

    josevalim committed
    Your application should *always* reference your application const (as Blog::Application) and Rails.application should be used just internally.
Commits on Jun 27, 2010
  1. @josevalim

    A few changes were done in this commit:

    josevalim committed
    * Added :autoload to engines path API and redefine usage to be in sync with 6f83a50;
    * Do not autoload code in *lib* for applications (now you need to explicitly require them). This makes an application behave closer to an engine (code in lib is still autoloaded for plugins);
    * Always autoload code in app/ for engines and plugins. This makes engines behave closer to an application and should allow us to get rid of the unloadable hack required when controllers inside engines inherit from ApplicationController;
Commits on Jun 24, 2010
  1. @jeremy
  2. @jeremy
Commits on Jun 23, 2010
  1. @fxn
Commits on Jun 20, 2010
  1. @josevalim
  2. @josevalim
  3. @josevalim
Commits on Jun 1, 2010
  1. @josevalim

    Add lib to load paths when application is inherited to be able to loa…

    josevalim committed
    …d lib code during configuration.
Commits on May 29, 2010
  1. @josevalim
  2. @wycats

    Removing Metal from Rails 3.

    wycats committed
    If you have existing Metals, you have a few options:
    * if your metal behaves like a middleware, add it to the
      middleware stack via config.middleware.use. You can use
      methods on the middleware stack to control exactly where
      it should go
    * if it behaves like a Rack endpoint, you can link to it
      in the router. This will result in more optimal routing
      time, and allows you to remove code in your endpoint
      that matches specific URLs in favor of the more powerful
      handling in the router itself.
    For the future, you can use ActionController::Metal to get
    a very fast controller with the ability to opt-in to specific
    controller features without paying the penalty of the full
    controller stack.
    Since Rails 3 is closer to Rack, the Metal abstraction is
    no longer needed.
Something went wrong with that request. Please try again.