be2fd61137
Fixes #40031 While removing deprecated non-symbol access to nested `config_for` hashes in #37876, we also broke `config_for` for anyone using the [safe_yaml] gem. The problem is that `safe_yaml` patches `YAML.load` in a way that doesn't honor the `symbolize_names` options (I believe this is on purpose, to prevent symbol-based DOS attacks). In the description of #37876 there is mention of the fact that this was the first place in Rails we used `symbolize_names`, and that `deep_symbolize_keys` had been used in the past. This commit switches over to `deep_symbolize_keys` to allow `config_for` to continue working for people using [safe_yaml]. [safe_yaml]: https://rubygems.org/gems/safe_yaml |
||
---|---|---|
.. | ||
bin | ||
exe | ||
lib | ||
test | ||
.gitignore | ||
CHANGELOG.md | ||
MIT-LICENSE | ||
railties.gemspec | ||
Rakefile | ||
RDOC_MAIN.rdoc | ||
README.rdoc |
= Railties -- Gluing the Engine to the Rails Railties is responsible for gluing all frameworks together. Overall, it: * handles the bootstrapping process for a Rails application; * manages the +rails+ command line interface; * and provides the Rails generators core. == Download The latest version of Railties can be installed with RubyGems: * gem install railties Source code can be downloaded as part of the Rails project on GitHub * https://github.com/rails/rails/tree/master/railties == License Railties is released under the MIT license: * https://opensource.org/licenses/MIT == Support API documentation is at * https://api.rubyonrails.org Bug reports can be filed for the Ruby on Rails project here: * https://github.com/rails/rails/issues Feature requests should be discussed on the rails-core mailing list here: * https://discuss.rubyonrails.org/c/rubyonrails-core