Ensure legacy migrators are inserted at the beginning of the collection #73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While testing importing legacy Umbraco 7 content and schema into v16, I noticed it's become a little harder in recent versions to ensure the migrators are added in the correct order, because Deploy now adds quite a few migrators by default (e.g. to migrate property editors that were removed in v14, like Nested Content and Grid layout).
To ensure the legacy migrators are added before the default Deploy ones, you need to add them in a composer that runs before the Deploy one (which is different between Deploy Cloud and OnPrem). It's also important to add your own migrators after the Deploy ones (especially migrators like
ReplaceUnknownEditorDataTypeArtifactMigrator
, so Nested Content isn't replaced with a label), requiring you to use different composers:To fix this, I've updated the
AddLegacyMigrators()
methods to insert the required artifact and property type migrators (and aligned AddLegacyTypeResolver()` to insert as well).