Stop throwing an exception during field migration if the field is already migrated

Created on 24 January 2024, about 1 year ago
Updated 22 May 2024, 11 months ago

Problem/Motivation

When trying to migrate a non-entity reference field using the taxonomy_enum.migration service, the process fails with an exception.

Proposed resolution

This check should be loosened to not throw an exception if the field type is taxonomy_enum, which means the migration has already been done.

🐛 Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

🇧🇪Belgium dieterholvoet Brussels

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024