Remove usages of MigrateSkipProcessException from core process plugins

Created on 2 November 2021, over 3 years ago
Updated 3 March 2024, about 1 year ago

Problem/Motivation

Using exceptions as signals to pass information back to the calling function is bad practice. In ✨ Allow process plugins to stop further processing on a pipeline RTBC We are looking at providing a way for a plugin to declare itself final (i.e. no process plugins after it in the same pipeline should run). Once this is committed to core, process pipelines that currently throw a MigrateSkipProcessException could accomplish the same feat by declaring themselves final and returning NULL.

Steps to reproduce

Proposed resolution

Refactor core process plugins to use this method instead of signaling with a skip process exception.

Remaining tasks

✨ Allow process plugins to stop further processing on a pipeline RTBC
Remove remaining usages from core process plugins.

User interface changes

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Fixed

Version

11.0 πŸ”₯

Component
MigrationΒ  β†’

Last updated 6 days ago

Created by

πŸ‡ΊπŸ‡ΈUnited States mikelutz Michigan, USA

Live updates comments and jobs are added and updated live.
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