diff options
| author | Les Nightingill <codehacker@comcast.net> | 2012-04-25 09:40:09 -0700 |
|---|---|---|
| committer | Les Nightingill <codehacker@comcast.net> | 2012-04-25 09:40:09 -0700 |
| commit | 047600157a1a7d2ec3e3afa7c90e539f94b37aa5 (patch) | |
| tree | bea5b8a040d37898f9ca68e03b915e90d3b68ef9 /guides | |
| parent | 4a3ce153f1e05c9c590e9ee74e818649336d929f (diff) | |
| download | rails-047600157a1a7d2ec3e3afa7c90e539f94b37aa5.tar.gz rails-047600157a1a7d2ec3e3afa7c90e539f94b37aa5.tar.bz2 rails-047600157a1a7d2ec3e3afa7c90e539f94b37aa5.zip | |
adds a mention of the fact that an engine's lib/assets directory is also on the load path
Diffstat (limited to 'guides')
| -rw-r--r-- | guides/source/engines.textile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/engines.textile b/guides/source/engines.textile index 36210aedb0..71bcf6b713 100644 --- a/guides/source/engines.textile +++ b/guides/source/engines.textile @@ -695,7 +695,7 @@ If a template is rendered from within an engine and it's attempting to use one o h4. Assets -Assets within an engine work in an identical way to a full application. Because the engine class inherits from +Rails::Engine+, the application will know to look up in the engine's +app/assets+ directory for potential assets. +Assets within an engine work in an identical way to a full application. Because the engine class inherits from +Rails::Engine+, the application will know to look up in the engine's +app/assets+ and +lib/assets+ directories for potential assets. Much like all the other components of an engine, the assets should also be namespaced. This means if you have an asset called +style.css+, it should be placed at +app/assets/stylesheets/[engine name]/style.css+, rather than +app/assets/stylesheets/style.css+. If this asset wasn't namespaced, then there is a possibility that the host application could have an asset named identically, in which case the application's asset would take precedence and the engine's one would be all but ignored. |