rails--rails/railties/CHANGELOG.md

• Deprecate Rails::DBConsole#config

Rails::DBConsole#config is deprecated without replacement. Use Rails::DBConsole.db_config.configuration_hash instead.

*Eileen M. Uchitelle*, *John Crepezzi*

• Rails.application.config_for merges shared configuration deeply.

  # config/example.yml
  shared:
    foo:
      bar:
        baz: 1
  development:
    foo:
      bar:
        qux: 2
  

  # Previously
  Rails.application.config_for(:example)[:foo][:bar] #=> { qux: 2 }
  
  # Now
  Rails.application.config_for(:example)[:foo][:bar] #=> { baz: 1, qux: 2 }
  

  Yuhei Kiriyama

• Remove access to values in nested hashes returned by Rails.application.config_for via String keys.

  # config/example.yml
  development:
    options:
      key: value
  

  Rails.application.config_for(:example).options
  

  This used to return a Hash on which you could access values with String keys. This was deprecated in 6.0, and now doesn't work anymore.

  Étienne Barrié

• Configuration files for environments (config/environments/*.rb) are now able to modify autoload_paths, autoload_once_paths, and eager_load_paths.

  As a consequence, applications cannnot autoload within those files. Before, they technnically could, but changes in autoloaded classes or modules had no effect anyway in the configuration because reloading does not reboot.

  Ways to use application code in these files:

  • Define early in the boot process a class that is not reloadable, from which the application takes configuration values that get passed to the framework.

    # In config/application.rb, for example.
    require "#{Rails.root}/lib/my_app/config"
    
    # In config/environments/development.rb, for example.
    config.foo = MyApp::Config.foo
    

  • If the class has to be reloadable, then wrap the configuration code in a to_prepare block:

    config.to_prepare do
      config.foo = MyModel.foo
    end
    

    That assigns the latest MyModel.foo to config.foo when the application boots, and each time there is a reload. But whether that has an effect or not depends on the configuration point, since it is not uncommon for engines to read the application configuration during initialization and set their own state from them. That process happens only on boot, not on reloads, and if that is how config.foo worked, resetting it would have no effect in the state of the engine.

  Allen Hsu & Xavier Noria

• Support using environment variable to set pidfile.

  Ben Thorner

Please check 6-0-stable for previous changes.