You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we get a depreciation warning which indicates that you use the method changed? which will be changed in future.
DEPRECATION WARNING: The behavior of `changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes?` instead.
We get this error because we update the model in an after_create callback which also uses thinking sphinx.
I believe this happens because TS fires its own change to the model (I'm presuming you're using deltas), which means there's another full cycle of callbacks in the inner save - and in there, it's calling changed? within the before_save. Rails' deprecation warning doesn't distinguish about the inner callback within the outer callback.
Hello,
we get a depreciation warning which indicates that you use the method
changed?
which will be changed in future.We get this error because we update the model in an
after_create
callback which also uses thinking sphinx.More information which methods will change can be found here rails/rails#25337 (comment)
The text was updated successfully, but these errors were encountered: