-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid history tracker with custom changes_method #159
Comments
@dblock Just now I checked, since I defined |
But wasn't that the whole point? I guess I don't understand what the original intent was anymore :) |
@dblock I think we can't fix this as the user modifies changes happened on the object using |
Backup. What did you want to happen in your initial example? I mean what was the purpose of |
The purpose of |
Ok, I understand. I think this should work. I would track where the Maybe write actual specs first where you do a |
The above spec yields following output:
History Tracker on creation:
History Tracker on updation:
Updation history trackers inserts with empty
modified
value. Actually it shouldn't empty.The text was updated successfully, but these errors were encountered: