…ping with Rails 4.0.
Conflicts: actionmailer/lib/action_mailer/base.rb activesupport/lib/active_support/configurable.rb activesupport/lib/active_support/core_ext/module/deprecation.rb guides/source/action_controller_overview.md guides/source/active_support_core_extensions.md guides/source/ajax_on_rails.textile guides/source/association_basics.textile guides/source/upgrading_ruby_on_rails.md While resolving conflicts, I have chosen to ignore changes done in docrails at some places - these will be most likely 1.9 hash syntax changes.
This allow the users to do: config.action_mailer.queue = MyQueue.new and class UsersMailer < ActionMailer::Base self.queue = MyQueue.new end
…mespaces The new option allows any Ruby namespace to be registered and set up for eager load. We are effectively exposing the structure existing in Rails since v3.0 for all developers in order to make their applications thread-safe and CoW friendly.
…il and instead implement smarter versions allowing for string class names, also added proper Railtie support with tests. Signed-off-by: José Valim <firstname.lastname@example.org>
…rb and use helper(:all) just after that
… hook 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.
…ties::RoutesHelper to AbstractController::Railties::RoutesHelpers
…ude engine's ones for controllers inside isolated namespace
…rameworks like ActiveRecord and ActiveResource to log outsude Rails::Application [#4816 state:resolved]
…loads before anything else
…ode that should run during framework load do: ActiveSupport.on_load(:action_controller) do # Code run in the context of AC::Base end
…t, remove railtie_name and engine_name and allow to set the configuration object.
add lazy_load_hooks.rb, which allows us to declare code that should be run at some later time. For instance, this allows us to defer requiring ActiveRecord::Base at boot time purely to apply configuration. Instead, we register a hook that should apply configuration once ActiveRecord::Base is loaded. With these changes, brings down total boot time of a new app to 300ms in production and 400ms in dev. TODO: rename base_hook
…vide ActionMailer#default_url_options= Signed-off-by: Jeremy Kemper <email@example.com>
…always uses AS.
…o paths, load active_support/railtie since we need it and ensure default logger is set before config.