Problem/Motivation
Using exceptions as signals to pass information back to the calling function is bad practice. In #3245997: Allow process plugins to stop further processing on a pipeline 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
#3245997: Allow process plugins to stop further processing on a pipeline
Remove remaining usages from core process plugins.
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3247329
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3247329-remove-usages-of
changes, plain diff MR !6148
Comments
Comment #6
mikelutz#3245997: Allow process plugins to stop further processing on a pipeline has now been merged and this issue is no longer postponed.
Comment #8
mikelutzComment #9
smustgrave commentedTest coverage definitely appears to be there https://git.drupalcode.org/issue/drupal-3247329/-/jobs/625221
Seeing as the task came from one of the migration submaintainers think that sign off is good.
Issue summary is complete and tests all green.
LGTM +1 RTBC.
per the new approach for #needs-review-queue-initative going to leave in NR for additional eyes. If no one does after a few days I'll mark it.
Comment #10
smustgrave commentedBeen a few days and don't want the issue to stale going to mark it.
Comment #11
longwaveCommitted e853205 and pushed to 11.x. Thanks!