diff options
| author | Ryan Bigg <radarlistener@gmail.com> | 2012-02-13 17:08:15 +1300 |
|---|---|---|
| committer | Ryan Bigg <radarlistener@gmail.com> | 2012-02-16 08:29:53 -0500 |
| commit | 7bdfc47da10c8d14f3b938b8b00280c782bc9d80 (patch) | |
| tree | 5be76b99c3156488fff799b6a1cdf0773f70edb1 /railties/guides | |
| parent | 6a2cf4cc3a3d2b187f8495ecf9d519c29a672a11 (diff) | |
| download | rails-7bdfc47da10c8d14f3b938b8b00280c782bc9d80.tar.gz rails-7bdfc47da10c8d14f3b938b8b00280c782bc9d80.tar.bz2 rails-7bdfc47da10c8d14f3b938b8b00280c782bc9d80.zip | |
[engines guide] Elaborate on isolate_namespace functionality
Diffstat (limited to 'railties/guides')
| -rw-r--r-- | railties/guides/source/engines.textile | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/railties/guides/source/engines.textile b/railties/guides/source/engines.textile index 1a423ab6de..856a04e90f 100644 --- a/railties/guides/source/engines.textile +++ b/railties/guides/source/engines.textile @@ -73,7 +73,13 @@ end By inheriting from the +Rails::Engine+ class, this gem notifies Rails that there's an engine at the specified path, and will correctly mount the engine inside the application, performing tasks such as adding the +app+ directory of the engine to the load path for models, controllers and views. -The +isolate_namespace+ method here deserves special notice. This call is responsible for isolating the controllers, models, routes and other things into their own namespace. Without this, there is a possibility that the engine's components could "leak" into the application, causing unwanted disruption. It is recommended that this line be left within this file. +The +isolate_namespace+ method here deserves special notice. This call is responsible for isolating the controllers, models, routes and other things into their own namespace, away from similar components inside hte application. Without this, there is a possibility that the engine's components could "leak" into the application, causing unwanted disruption, or that important engine components could be overriden by similarly named things within the application. + +NOTE: It is *highly* recommended that the +isolate_namespace+ line be left within the +Engine+ class definition. + +The +isolate_namespace+ line will cause the models, controllers and views to be namespaced for the engine. What this means is that a model called +Post+ would instead be called +Blorgh::Post+, a controller called +PostsController+ would be +Blorgh::Postscontroller+ and the views for that controller would not be at +app/views/posts+, but rather +app/views/blorgh/posts+. In addition to this, the table for the model is namespaced, becoming +blorgh_posts+, rather than simply +posts+. + +Finally, routes will also be isolated within the engine. This is discussed later in the "Routes":#routes section of this guide. h5. +app+ directory |