As a developer, if I fetch a resource from the server, update that resource on the server, then update the local resource I have, the old attributes that were stored in the local resource (and were changed on the server) will then be sent back to the server to change again.
Why? Because update always sends all attributes, not just the dirty ones
Objectives
Add dirty checking to Base, maintaining a prior version of each attribute and allowing methods for checking if any individual attribute changed, or to get all changed attributes
Add dirty checking to Association, so I can see if:
The definition of the relationship changed
The data of any relationship resource changed (checks if autosaving association)
Stories
As a developer, if I fetch a resource from the server, update that resource on the server, then update the local resource I have, the old attributes that were stored in the local resource (and were changed on the server) will then be sent back to the server to change again.
Why? Because
update
always sends all attributes, not just the dirty onesObjectives
Base
, maintaining a prior version of each attribute and allowing methods for checking if any individual attribute changed, or to get all changed attributesAssociation
, so I can see if: