aboutsummaryrefslogtreecommitdiffstats
path: root/actionpack/test/controller/force_ssl_test.rb
diff options
context:
space:
mode:
authorRyuta Kamizono <kamipo@gmail.com>2018-06-09 17:30:00 +0900
committerRyuta Kamizono <kamipo@gmail.com>2018-06-18 19:08:41 +0900
commitcad0b7d91dbc5abf4b0d7fdbcf2d0620557a3b0f (patch)
tree9931a8eb4a452c9de635661cad42353750452c43 /actionpack/test/controller/force_ssl_test.rb
parenta865f621ee934e8741001bbed1b487698e44d914 (diff)
downloadrails-cad0b7d91dbc5abf4b0d7fdbcf2d0620557a3b0f.tar.gz
rails-cad0b7d91dbc5abf4b0d7fdbcf2d0620557a3b0f.tar.bz2
rails-cad0b7d91dbc5abf4b0d7fdbcf2d0620557a3b0f.zip
Fix `touch` option to behave consistently with `Persistence#touch` method
`touch` option was added to `increment!` (#27660) and `update_counters` (#26995). But that option behaves inconsistently with `Persistence#touch` method. If `touch` option is passed attribute names, it won't update update_at/on attributes unlike `Persistence#touch` method. Due to changed from `Persistence#touch` to `increment!` with `touch` option, #31405 has a regression that `counter_cache` with `touch` option which is passed attribute names won't update update_at/on attributes. I think that the inconsistency is not intended. To get back consistency, ensure that `touch` option updates update_at/on attributes.
Diffstat (limited to 'actionpack/test/controller/force_ssl_test.rb')
0 files changed, 0 insertions, 0 deletions