mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
969577d960
Firstly, increment and decrement shouldn't care about the particulars of key expiry. They should only know that they have to pass that responsibility on to somewhere else. Secondly, it moves the key normalization back inside the instrumentation like it was originally. I think that matches the original design intention or at the very least it lets users catch haywire key truncation. Thirdly, it moves the changelog entry to the top of the file, where new entries go. I couldn't understand what the entry was saying so I tried to rewrite it. |
||
|---|---|---|
| .. | ||
| behaviors | ||
| stores | ||
| behaviors.rb | ||
| cache_entry_test.rb | ||
| cache_key_test.rb | ||
| cache_store_logger_test.rb | ||
| cache_store_namespace_test.rb | ||
| cache_store_setting_test.rb | ||
| local_cache_middleware_test.rb | ||