Content
View differences
Updated by Oliver Günther almost 8 years ago
user\#9177, user\#4710, user\#39106,
I just discussed with user\#87 wether or not we should activate `config.action_controller.perform_caching = true` in development.rb. Currently it is deactivated, and I know it like this.
However, user\#87 is defending the idea that it should be activated in order to be closer to production-like behaviour and is arguing that caching is part of the application. He goes even further and argues that it caching should be activated when running (feature?) specs.
Here you can see, that in Rails 5 the development.rb indeed changed, allowing for caching in development. However, I understand that is switched off by default. See
\[1\] A diff what got changed between rails 4 and rails 5 http://railsdiff.org/4.2.10/5.2.0
\[2\] An explanation https://blog.bigbinary.com/2016/01/25/caching-in-development-environment-in-rails5.html
Any opinions on that?
I just discussed with user\#87 wether or not we should activate `config.action_controller.perform_caching = true` in development.rb. Currently it is deactivated, and I know it like this.
However, user\#87 is defending the idea that it should be activated in order to be closer to production-like behaviour and is arguing that caching is part of the application. He goes even further and argues that it caching should be activated when running (feature?) specs.
Here you can see, that in Rails 5 the development.rb indeed changed, allowing for caching in development. However, I understand that is switched off by default. See
\[1\] A diff what got changed between rails 4 and rails 5 http://railsdiff.org/4.2.10/5.2.0
\[2\] An explanation https://blog.bigbinary.com/2016/01/25/caching-in-development-environment-in-rails5.html
Any opinions on that?