diff options
author | Claudi Martinez <claudix.kernel@gmail.com> | 2015-11-13 09:18:04 +0100 |
---|---|---|
committer | Claudi Martinez <claudix.kernel@gmail.com> | 2015-11-13 09:18:04 +0100 |
commit | 2ae24ddc31e706b0a7f5360cebe0e5c996eb6de4 (patch) | |
tree | a862ef11ce4782aef205868024b9836b3148273d /guides/source | |
parent | ef202f6b7d86adde84a7193bc5066b447054b76d (diff) | |
download | rails-2ae24ddc31e706b0a7f5360cebe0e5c996eb6de4.tar.gz rails-2ae24ddc31e706b0a7f5360cebe0e5c996eb6de4.tar.bz2 rails-2ae24ddc31e706b0a7f5360cebe0e5c996eb6de4.zip |
Improved explanation
Diffstat (limited to 'guides/source')
-rw-r--r-- | guides/source/engines.md | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/guides/source/engines.md b/guides/source/engines.md index e670962fe6..359796b1ff 100644 --- a/guides/source/engines.md +++ b/guides/source/engines.md @@ -241,10 +241,7 @@ applications into engines. NOTE: Because of the way that Ruby does constant lookup you may run into a situation where your engine controller is inheriting from the main application controller and -not your engine's application controller. Ruby will look in the ancestor chain for -constants and every class has `Object` as an ancestor, meaning that if the global -`ApplicationController` is loaded Ruby will return that and not call `const_missing` -and trigger the Rails autoloading mechanism. The best way to prevent this from +not your engine's application controller. Ruby is able to resolve the `ApplicationController` constant, and therefore the autoloading mechanism is not triggered. See the section [When Constants Aren't Missed](autoloading_and_reloading_constants.html#when-constants-aren-t-missed) of the [Autoloading and Reloading Constants](autoloading_and_reloading_constants.html) guide for further details. The best way to prevent this from happening is to use `require_dependency` to ensure that the engine's application controller is loaded. For example: |