diff options
| author | st0012 <stan001212@gmail.com> | 2019-04-24 00:22:33 +0800 |
|---|---|---|
| committer | st0012 <stan001212@gmail.com> | 2019-04-24 02:08:13 +0800 |
| commit | d63f9383a6dabfaffbb464409ed94b8d77f12a4f (patch) | |
| tree | e49144e0b2204218ba549cb2ca7c89501d188195 /actionpack/test/controller/form_builder_test.rb | |
| parent | 6a4eb3e75eabfe6c00ea60b845b487f70a350222 (diff) | |
| download | rails-d63f9383a6dabfaffbb464409ed94b8d77f12a4f.tar.gz rails-d63f9383a6dabfaffbb464409ed94b8d77f12a4f.tar.bz2 rails-d63f9383a6dabfaffbb464409ed94b8d77f12a4f.zip | |
Remove action_controller.perform_caching from api app's configs
As suggested in https://github.com/rails/rails/issues/35602#issuecomment-485833483, because we don't provide view caching and doesn't include `ActionController::Caching` for api apps, we should also avoid generating
```ruby
config.action_controller.perform_caching = true
```
for those api apps. So it won't confuse people.
**But because `perform_caching` will be `true` if not set, the behavior of the app would still be the same without these configs.**
Diffstat (limited to 'actionpack/test/controller/form_builder_test.rb')
0 files changed, 0 insertions, 0 deletions