Ensure all initializers are collections.
Plugins need to load before app initializers
Add Rails::Application pointer to the default app to add symmetry to …
Ensure environment config has higher priority than application ones.
Ensure helpers work from configured path.
Solve some pendencies.
Move configuration to subfolders.
Create configurable modules and ensure that they are added only on di…
Plugin is now an Engine.
First steps into making Plugin < Engine.
Extract Railtie load from application.
Break application.rb file in smaller chunks.
Extract routes reloading responsibilities from application and load t…
…hem just upon a request.
Ensure user set load paths have higher preference and move Bootstrap …
Get rid of initializers global and create i18n railtie.
Moved more configuration away from bootstrap.
Got tests working once again.
Add view paths to Engine setup.
Massive cleanup in Railties and load stack.
Make filter parameters based on request, so they can be modified for …
…anything in the middleware stack.
fixes the failure of config.plugins without :all option tests [#3718 …
Signed-off-by: José Valim <email@example.com>
Allow railties to specify generators paths.
Build middleware stack and reload routes after app initializers run
Set up subscriber on initialization.
Run railtie and plugin initializers before app specific ones
config.plugins should still work with an array of strings
Time zoning should be turned on by default with UTC
AppName::Application.root should work
Rails notifications are set through Railtie in each framework.
Some railties cleanup:
* Rename <framework>/rails.rb -> <framework>/railtie.rb
* Rails::Plugin -> Rails::Railtie
* Rails::Plugin::Vendored -> Rails::Plugin
Fully remove config.frameworks in favor of requires in boot.rb
Use the correct method for eager loading autoloads
Make plugins responsible for loading their own rake tasks
Signed-off-by: Carl Lerche <firstname.lastname@example.org>
Application object should instantiate non-vendored plugins