diff options
| author | yuuji.yaginuma <yuuji.yaginuma@gmail.com> | 2018-09-01 16:31:15 +0900 |
|---|---|---|
| committer | Yuji Yaginuma <yuuji.yaginuma@gmail.com> | 2018-09-04 20:06:54 +0900 |
| commit | fb3642b0caf42b0554a8fd0672943f4da1643b2c (patch) | |
| tree | f82e8de176f593602a44d45fbbf4d85d5ad325c0 /railties/lib/rails/info_controller.rb | |
| parent | 63c6943131189c902485f725b465b48ebea14b09 (diff) | |
| download | rails-fb3642b0caf42b0554a8fd0672943f4da1643b2c.tar.gz rails-fb3642b0caf42b0554a8fd0672943f4da1643b2c.tar.bz2 rails-fb3642b0caf42b0554a8fd0672943f4da1643b2c.zip | |
Respect config setting when output deprecation notice in rake tasks
The rake tasks which became deprecate now does not load the environment.
Therefore, even if the application specifies the behavior of deprecating,
the message is output to stderr ignoring the specification.
It seems that this is not the expected behavior.
We should respect the setting even in the rake tasks.
Diffstat (limited to 'railties/lib/rails/info_controller.rb')
0 files changed, 0 insertions, 0 deletions