mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
Patch for #1458 - [3.1.0.rc1] App plugins initialized before engines
and plugins inside engines It seems that plugins inside a Rails 3.1 application proper (i.e. in /vendor/plugins) are initialized before engines and plugins inside engines. After some debugging, I found the culprit in Rails::Application::Railties#all: def all(&block) @all ||= railties + engines + super @all.each(&block) if block @all end The call to super here implicitly passes the &block argument, which has the unfortunate side-effect of adding the plugin initializers first (in front of other railties and engines) in the case of Rails::Engine#initializers: def initializers initializers = [] railties.all { |r| initializers += r.initializers } initializers += super initializers end The solution here is to replace the super call with a call to #plugins.
This commit is contained in:
parent
be99ae78c9
commit
29dfe05e07
1 changed files with 1 additions and 1 deletions
|
@ -4,7 +4,7 @@ module Rails
|
|||
class Application < Engine
|
||||
class Railties < Rails::Engine::Railties
|
||||
def all(&block)
|
||||
@all ||= railties + engines + super
|
||||
@all ||= railties + engines + plugins
|
||||
@all.each(&block) if block
|
||||
@all
|
||||
end
|
||||
|
|
Loading…
Reference in a new issue