aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/application/per_request_digest_cache_test.rb
Commit message (Collapse)AuthorAgeFilesLines
* applies new string literal convention in railties/testXavier Noria2016-08-061-13/+13
| | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
* Make collection caching explicit.Kasper Timm Hansen2016-02-201-0/+2
| | | | | | | | | | | | Having collection caching that wraps templates and automatically tries to infer if they are cachable proved to be too much of a hassle. We'd rather have it be something you explicitly turn on. This removes much of the code and docs to explain the previous automatic behavior. This change also removes scoped cache keys and passing cache_options.
* move digest cache on to the DetailsKey objectAaron Patterson2016-02-181-2/+3
| | | | | | | | | | | | | This moves digest calculation cache on to the details key object. Before, the digest cache was a class level ivar, and one of the keys was the hash value of the details key object: https://github.com/rails/rails/blob/13c4cc3b5aea02716b7459c0da641438077f5236/actionview/lib/action_view/digestor.rb#L28 An object's hash value is not unique, so it's possible for this cache key to produce colliding keys with no resolution. This commit move cache on to the details key object itself, so we know that the digests are always unique per details key object.
* Make digest cache work in development.Kasper Timm Hansen2015-07-181-0/+63
Avoid computing the same fragment digest many times when looping over templates. The cache is cleared on every request so template changes are still picked up.