Dispatch a MigrateRowFailEvent when a row fails

Created on 4 March 2021, almost 4 years ago
Updated 9 February 2024, 11 months ago

Problem/Motivation

If, during a migration, a row fails to be imported, the error gets logged but there is no other way to trigger any other actions that might be of interest. The Migrate API dispatches events before and after saving a row, but nothing if a row fails.

Steps to reproduce

Any migration that has a row that fails.

Proposed resolution

I propose the creation and dispatching of a migrate.row_fail event, so that other parts of the system can subscribe and be informed.

Remaining tasks

  • Review
  • Add a change record
  • Write a release notes snippet

User interface changes

None.

API changes

A new event can be dispatched.

Data model changes

None.

Release notes snippet

โœจ Feature request
Status

Needs work

Version

11.0 ๐Ÿ”ฅ

Component
Migrationย  โ†’

Last updated about 13 hours ago

Created by

๐Ÿ‡ณ๐Ÿ‡ดNorway efpapado

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • Needs change record

    A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024