Using Protolith, require all registered objects to be Protolith compatible (provide a Protolith codec), and integrate with Tectonic to allow for simple "Updates" to be applied to configs.
Automatic updates would be applied by having every config type specify a version key, with updates being applied between versions. Updates would simply provide optics onto old config schemas which "translate" to new config schema values. These translation optics would then be composed together automatically to incrementally update old config schemas.
Using Protolith, require all registered objects to be Protolith compatible (provide a Protolith codec), and integrate with Tectonic to allow for simple "Updates" to be applied to configs.
Automatic updates would be applied by having every config type specify a
versionkey, with updates being applied between versions. Updates would simply provide optics onto old config schemas which "translate" to new config schema values. These translation optics would then be composed together automatically to incrementally update old config schemas.