gum-project-versioning

To handle Gum schema migration, you bump the version enum and apply backward-compatibility shims using XmlSerializer overrides. This ensures .gumx files load correctly across different tool versions when altering the shape of serialized classes.

You should bump the .gumx version number when altering the shape of serialized classes like ElementSave. The decision framework uses the GumxVersions enum to track schema changes and determine if backward-compatibility shims are required for older files.

Gum reacts to mismatched file versions at load-time by checking the version enum. It applies migration shims via XmlSerializer overrides for older files, while newer file versions trigger specific load compatibility behaviors to prevent data corruption.

The best way to add optional fields during Gum schema versioning is to bump the GumxVersions enum and implement a shim pattern. This approach uses XmlSerializer overrides to ensure backward compatibility without breaking existing .gumx project loads.

Yes, understanding XmlSerializer overrides is required for Gum project migration. You need this knowledge to implement shims and handle list versus array serialization when maintaining load compatibility across tool versions.