aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRory O’Kane <rory@roryokane.com>2012-05-22 15:50:19 -0300
committerRory O’Kane <rory@roryokane.com>2012-05-22 15:50:19 -0300
commitf09c84ca26a73304943421d473faa3ea808d18ce (patch)
tree41c50602f970eb612392b3f55ebe778d6ceeffe8
parenteb2c0a4f712b015bf6886286efd6e5b2eeaf54aa (diff)
downloadrails-f09c84ca26a73304943421d473faa3ea808d18ce.tar.gz
rails-f09c84ca26a73304943421d473faa3ea808d18ce.tar.bz2
rails-f09c84ca26a73304943421d473faa3ea808d18ce.zip
clarified how file naming affects load order of initializers
-rw-r--r--guides/source/configuring.textile2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/configuring.textile b/guides/source/configuring.textile
index f114075cae..af46538bf5 100644
--- a/guides/source/configuring.textile
+++ b/guides/source/configuring.textile
@@ -585,7 +585,7 @@ After loading the framework and any gems in your application, Rails turns to loa
NOTE: You can use subfolders to organize your initializers if you like, because Rails will look into the whole file hierarchy from the initializers folder on down.
-TIP: If you have any ordering dependency in your initializers, you can control the load order by naming. For example, +01_critical.rb+ will be loaded before +02_normal.rb+.
+TIP: If you have any ordering dependency in your initializers, you can control the load order through naming. Initializer files are loaded in alphabetical order by their path. For example, +01_critical.rb+ will be loaded before +02_normal.rb+.
h3. Initialization events