Release 0.6.0
With version 0.6.0 we added three new features:
- Changes to scalar values will now only be seen as a change if the new value is actually different. See #17 for details. Thanks for @dannosaur for the report the old behaviour does not match user expectation.
- There are now utility methods to restore original field values or a copy of the original model state. See #11 for details.
- You may now use change markers to mark objects as changed without a field actually being changes. This can be useful when for example propagating changes state from child objects to its parents. See #10 for details.
- The README was updated to reflect those new features. Also some example code was added to chow how
set_changed(...)
works.