aboutsummaryrefslogtreecommitdiffstats
path: root/activesupport
diff options
context:
space:
mode:
authorPiotr Sarnacki <drogus@gmail.com>2012-05-27 12:28:26 +0200
committerPiotr Sarnacki <drogus@gmail.com>2012-05-27 14:13:45 +0200
commit0e69705b0fc7501bada74b3ca023ae7f7b2b8592 (patch)
tree8a3343074b09e1fa2584887257efb153e1cb1525 /activesupport
parent81ad94e0ac199cbae6c7bdc0380b2c821c3c56a5 (diff)
downloadrails-0e69705b0fc7501bada74b3ca023ae7f7b2b8592.tar.gz
rails-0e69705b0fc7501bada74b3ca023ae7f7b2b8592.tar.bz2
rails-0e69705b0fc7501bada74b3ca023ae7f7b2b8592.zip
Fix railties_order when application object is passed
railites_order method, introduced in 40b19e0, had a bug that was causing loading application instance twice in initializers if railties_order already included application instance. So for example railties_order = [Foo::Engine, :main_app, Bar::Engine] would result in such railties array: [MyApp::Application, Foo::Engine, MyAppApplication, Bar::Engine] In order to fix it, we need to check for existence of application in both railties_order and railties arrays.
Diffstat (limited to 'activesupport')
0 files changed, 0 insertions, 0 deletions