Closed McManning closed 4 years ago
I need some references on this one - because slapping a version field on Graph is fine and all but if changes are drastic enough to break deserialization then it's not like it'd help.
Found an example in Microsoft's MR toolkit, maybe applicable here:
This was added (a few commits ago - forgot to tag) as Graph.m_Version
. I can refer to Microsoft's MR project if I ever need to figure out upgrade paths.
Add a version number baked onto Graph so that migrations can be safely handled in case of backwards breaking changes to how graphs are persisted.