kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

Fix strange sentence in classic_mode guide [skip ci]

Browse source 
The following sentence doesn't make sense:

  But using `autoload_paths` on its own  in the past (before Rails 5)
  developers might configure `autoload_paths` to add in extra locations...

This changes it to the following:

  Before Rails 5 developers might configure `autoload_paths` to add in
  extra locations...

It also formats the text to use shorter line lengths.
This commit is contained in:
Petrik 2020-09-03 11:43:37 +02:00
parent 90216abe12
commit c695ef7b2f
1 changed files with 8 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
guides/source/autoloading_and_reloading_constants_classic_mode.md
View file

@ -477,8 +477,14 @@ How files are autoloaded depends on `eager_load` and `cache_classes` config sett
* In **production**, however, you want consistency and thread-safety and can live with a longer boot time. So `eager_load` is set to `true`, and then during boot (before the app is ready to receive requests) Rails loads all files in the `eager_load_paths` and then turns off auto loading (NB: autoloading may be needed during eager loading). Not autoloading after boot is a `good thing`, as autoloading can cause the app to be have thread-safety problems. * In **production**, however, you want consistency and thread-safety and can live with a longer boot time. So `eager_load` is set to `true`, and then during boot (before the app is ready to receive requests) Rails loads all files in the `eager_load_paths` and then turns off auto loading (NB: autoloading may be needed during eager loading). Not autoloading after boot is a `good thing`, as autoloading can cause the app to be have thread-safety problems.
* In **test**, for speed of execution (of individual tests) `eager_load` is `false`, so Rails follows development behaviour. * In **test**, for speed of execution (of individual tests) `eager_load` is `false`, so Rails follows development behaviour.
What is described above are the defaults with a newly generated Rails app. There are multiple ways this can be configured differently (see [Configuring Rails Applications](configuring.html#rails-general-configuration). What is described above are the defaults with a newly generated Rails app.
). But using `autoload_paths` on its own in the past (before Rails 5) developers might configure `autoload_paths` to add in extra locations (e.g. `lib` which used to be an autoload path list years ago, but no longer is). However this is now discouraged for most purposes, as it is likely to lead to production-only errors. It is possible to add new locations to both `config.eager_load_paths` and `config.autoload_paths` but use at your own risk. There are multiple ways this can be configured differently (see [Configuring
Rails Applications](configuring.html#rails-general-configuration).). Before
Rails 5 developers might configure `autoload_paths` to add in extra locations
(e.g. `lib` which used to be an autoload path list years ago, but no longer
is). However this is now discouraged for most purposes, as it is likely to
lead to production-only errors. It is possible to add new locations to both
`config.eager_load_paths` and `config.autoload_paths` but use at your own risk.
See also [Autoloading in the Test Environment](#autoloading-in-the-test-environment). See also [Autoloading in the Test Environment](#autoloading-in-the-test-environment).