Feature - mapping config

[KevinJump]

Ability to tell the migrator how to map properties in config .

e.g.

• how to get from grid to custom block list or something
• or leblender to something

A bigger one, will prob not make the first release !

Will likely be a bit complex, but the idea that in a config file somewhere you can say "this is the structure i have", and "this is the one i want", we have similar (albeit much simpler) in Translation manageer, it could be wrapped for common use cases so it might just be a how to get the grid from a to b- or nested content i want to map to x.

lots of things to think about with this one.

[leekelleher]

So far my general stance (particularly for a free-version of uSync Migrations) has been, if you're going to do a heavy-bespoke migration, then hook into the SyncMigratedNotification<Content> notification-even and do you thang!

I worry that introducing this would demand more support, especially for those Vorto-Grid-DTGE-Archetype combos that want to go Variant, Block Grid, et al.

That said, if you have ideas, (from Translation Manager), all cool and the gang.

[KevinJump]

Yeah i suspect this is going to be on the complex site of things, at the moment (and certainly for any initial release) this isn't going to be doable with config. but the extra things added for vorto might help.

• ISyncReplacablePropertyMigrator lets you tell the process that this datatype is actually replaced by something else and shouldn't be imported

vorto uses this because the vorto property is just a wrapper of another datatype, so the migrator uses this interface to tell the core process - for example when you see this datatypes id, replace it with the textbox property it wraps.