aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/engine/configuration.rb
Commit message (Collapse)AuthorAgeFilesLines
* Remove asset paths from eager_load_paths and autoload_pathsGannon McGibbon2018-11-091-1/+3
| | | | | Remove `app/assets` and `app/javascript` from `eager_load_paths` and `autoload_paths`.
* Revert "Merge pull request #33970 from rails/eager-url-helpers"schneems2018-10-031-1/+1
| | | | | | | Until #34050 can be resolved This reverts commit 7f870a5ba2aa9177aa4a0e03a9d027928ba60e49, reversing changes made to 6556898884d636c59baae008e42783b8d3e16440.
* Eager load supports individual filesAaron Patterson2018-09-261-1/+1
| | | | Also we want to eager load routes before anything else.
* [Railties] require_relative => requireAkira Matsuda2017-10-211-1/+1
| | | | This basically reverts 618268b4b9382f4bcf004a945fe2d85c0bd03e32
* Adding frozen_string_literal pragma to Railties.Pat Allan2017-08-141-0/+2
|
* [Railties] require => require_relativeAkira Matsuda2017-07-011-1/+1
|
* Add more rubocop rules about whitespacesRafael Mendonça França2016-10-291-1/+1
|
* applies new string literal convention in railties/libXavier Noria2016-08-061-1/+1
| | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
* Inject Rails' channel paths in engine.Kasper Timm Hansen2016-02-141-0/+1
| | | | | | | | | | | | | We were explicitly referencing Rails.root in ActionCable::Server::Configuration.initialize, thereby coupling ourselves to Rails. Instead add `app/channels` to Rails' app paths and assign the existent files to `channel_paths`. Users can still append to those load paths with `<<` and `push` in `config/application.rb`. This means we can remove the custom `Dir` lookup in `channel_paths` and the Rails and root definitions in the tests.
* `config.generators` should be docummented since it is public APIRafael Mendonça França2015-10-221-1/+1
| | | | [ci skip]
* Stop modifying global variableseileencodes2015-09-291-6/+3
| | | | | | Allocating a new middleware proxy in each application configuration and then merging the app specific config with the global config when the app is built.
* actually autoload all second-level directories called `app/*/concerns`Alex Robbin2014-12-261-4/+1
|
* Revert "Deprecate the `eager_load_paths` configuration"Andrew White2013-02-191-15/+9
| | | | | | | | | | | Because of the possibility of lib being unintentionally eager loaded it's been agreed that we'll leave autoload paths and eager load paths separate for Rails 4.0. This reverts commit 0757b3388ffe4f44b60de950d40e18ef05055931. Conflicts: railties/CHANGELOG.md
* Deprecate the `eager_load_paths` configurationAndrew White2013-01-241-9/+15
| | | | | | | | | | Since the default in Rails 4.0 is to run in 'threadsafe' mode we need to eager load all of the paths in `autoload_paths` so we alias `eager_load_paths` to it. This may have unintended consequences if you have added 'lib' to `autoload_paths` such as loading unneeded code or code intended only for development and/or test environments. If this applies to your application you should thoroughly check what is being eager loaded.
* Add app/models/concerns and app/controllers/concerns to the default ↵David Heinemeier Hansson2012-12-181-0/+9
| | | | directory structure and load path
* Use Ruby 1.9 Hash syntax in railtiesRobin Dupret2012-10-141-15/+15
|
* Revert "Allow loading external route files from the router"José Valim2012-06-291-1/+0
| | | | | | | | | | | | | | This reverts commit 6acebb38bc0637bc05c19d87f8767f16ce79189b. Usage of this feature did not reveal any improvement in existing apps. Conflicts: actionpack/lib/action_dispatch/routing/mapper.rb guides/source/routing.textile railties/lib/rails/engine.rb railties/lib/rails/paths.rb railties/test/paths_test.rb
* Revert "require the constants we use. ensure that root always returns a ↵Aaron Patterson2012-05-231-2/+1
| | | | | | Pathname" This reverts commit d77b576c0330d8b1c6189cb94814382ce32baab6.
* require the constants we use. ensure that root always returns a PathnameAaron Patterson2012-05-231-1/+2
|
* Merge pull request #3359 from mrreynolds/datamapper_naming_fixRafael Mendonça França2012-05-191-1/+1
|\ | | | | Fixed DataMapper namings in symbols and constants.
| * Fixed DataMapper namings in symbols and constants.Robert Glaser2011-10-181-1/+1
| |
* | Make files in paths consistentYehuda Katz2012-04-251-1/+1
| |
* | Allow loading external route files from the routerJose and Yehuda2012-04-251-1/+2
| | | | | | | | | | | | | | | | | | This feature enables the ability to load an external routes file from the router via: draw :filename External routes files go in +config/routes+. This feature works in both engines and applications.
* | Rails::Plugin has goneSantiago Pastorino2012-01-031-2/+0
| |
* | fix nodocsVijay Dev2011-12-091-1/+1
|/
* Need it declared tooDavid Heinemeier Hansson2011-05-101-0/+1
|
* Remove the ability for engines to serve assets from the public directory.José Valim2011-04-151-8/+1
|
* Booya, sprockets now works from Engines.José Valim2011-04-151-0/+2
|
* Make deep copy of application generators on engine initialization.Piotr Sarnacki2010-11-021-1/+1
| | | | | Otherwise nested hashes will be same objects for both application and engine, which will result in overwriting each others values on changes.
* Use application's generators defaults as engine defaults to not force users ↵Piotr Sarnacki2010-11-021-0/+1
| | | | to manually set it
* Provide a cleaner syntax for paths configuration that does not rely on ↵José Valim2010-10-061-22/+21
| | | | method_missing.
* Deprecate generators in Railties. You should use app_generators instead.José Valim2010-10-021-3/+25
|
* Add helper for loading seed data for engine and applicationPiotr Sarnacki2010-09-201-0/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Include all helpers from non-namespaced enginesPiotr Sarnacki2010-09-031-0/+1
|
* Get rid of static_paths method and instead configure paths for ↵Piotr Sarnacki2010-09-031-0/+4
| | | | ActionDispatch::Static in initializers
* Added Rails.application.config.paths.db.migrate to remove hardcoded ↵Piotr Sarnacki2010-09-031-0/+2
| | | | db/migrate paths
* Added ability to set asset_path for enginesPiotr Sarnacki2010-09-031-1/+1
|
* Allow Engines loading its own environment file from config/environmentsPiotr Sarnacki2010-09-031-0/+1
|
* Removed ActionDispatch::Static, but left empty MiddlewareStack to unify app ↵Piotr Sarnacki2010-09-031-2/+1
| | | | method between Engine and Application
* Engine can now serve files with ActionDispatch::StaticPiotr Sarnacki2010-09-031-2/+3
|
* Engine can now load its own pluginsPiotr Sarnacki2010-09-031-1/+3
|
* Made Engine valid rack app with its own middleware stackPiotr Sarnacki2010-09-031-0/+2
|
* Revert "Put lib back on the autoload path"José Valim2010-08-041-1/+1
| | | | | | This was causing engines/gems to eager load everything in lib. Another fix is comming soon. This reverts commit 02a5842cd09bd75de4c2fdb6b474c6c0ff163ebf.
* Put lib back on the autoload pathwycats2010-08-031-1/+1
|
* Add a header that tells Internet Explorer (all versions) to use the best ↵wycats2010-07-271-1/+1
| | | | | | 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.
* A few changes were done in this commit:José Valim2010-06-281-2/+2
| | | | | | * Added :autoload to engines path API and redefine usage to be in sync with 6f83a5036d8a9c3f8ed7; * 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;
* renames load_(once_)paths to autoload_(once_)paths in dependencies and configXavier Noria2010-06-241-5/+5
|
* Revert "files in the lib directory are no longer autoloaded"Xavier Noria2010-06-211-5/+1
| | | | | | | This patch is not consistent since it leaves similar directories in load_paths, needs more thought. This reverts commit b5fe014fdcc285f3bcb8779c4f7cfbc5a820856f.
* files in the lib directory are no longer autoloadedXavier Noria2010-06-211-1/+5
| | | | | | | | | | | Conceptually, the lib directory is closer 3rd party libraries than to the application itself. Thus, Rails adds it to Ruby's load path ($LOAD_PATH, $:) but it is no longer included in dependencies' load paths. To enable autoloading back put this in your config/application.rb config.load_paths += %W( #{config.root}/lib )
* Removing Metal from Rails 3. wycats2010-05-291-1/+0
| | | | | | | | | | | | | | | | | | | | 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-03 02:47:20 +0000