Closed Eseperio closed 6 years ago
Hi! Yes, I agree with you. Could you please make a pull request?
Well, the title is wrong. My PR does not fix this problem, it ensures that skipped attributes are ignored before comparing value. I think it has no sense to register the history of a field that generates itself.
Skip attributes behavior should be done before comparing values.
If you use an expression in other behaviors history will fail.
Explanation.
When a behavior uses a db expression to set the value, history behavior fails. That is because it expects that all values are comparable.