diff options
| author | eileencodes <eileencodes@gmail.com> | 2017-07-01 14:22:28 -0400 |
|---|---|---|
| committer | eileencodes <eileencodes@gmail.com> | 2017-07-01 14:53:21 -0400 |
| commit | 608ebccf8f6314c945444b400a37c2d07f21b253 (patch) | |
| tree | cd5bf26acf9e801bcdb6dec38a30d891885f1c7d /Gemfile.lock | |
| parent | c197418bdbb0c5546964bfc234d056edaa69eae2 (diff) | |
| download | rails-608ebccf8f6314c945444b400a37c2d07f21b253.tar.gz rails-608ebccf8f6314c945444b400a37c2d07f21b253.tar.bz2 rails-608ebccf8f6314c945444b400a37c2d07f21b253.zip | |
Deprecate and replace `set_state` method
`set_state` was directly setting the transaction state instance
variable. It's better to set the state via specific methods (`rollback!`
and `commit!` respectively.
While undocumented and untested, it's possible someone is using
`set_state` in their app or gem so I've added a deprecation notice to
it.
No where in the app do we use `nullify!` but I wanted to keep existing
behavior while replacing the method with a better pattern.
Diffstat (limited to 'Gemfile.lock')
0 files changed, 0 insertions, 0 deletions