Add missing source item event

+++ b/src/Event/MigrateEvents.php
@@ -27,4 +27,17 @@ final class MigrateEvents {
+   * implements a listener, the MigrateExecutable listener (with 1000 weight)

Is this really true? It would be if someone where using migrate tool's executable, but not generically speaking all executables.

Is this really true? It would be if someone where using migrate tool's executable, but not generically speaking all executables.

Indeed, this only applies when the migrate executable with the required change to trigger the event is used.

It is a strange to point to a migrate_tools class from here, since that module depends on migrate_plus.
I would say it is better if we also declare the event there.

I am adding a new patch with the change here just in case, but we probably want to close this issue, and add the change here directly into #2809433: Migrate support for deleting items no longer in the incoming data.

+++ b/src/Event/MigrateEvents.php
@@ -27,4 +27,21 @@ final class MigrateEvents {
+   * \Drupal\migrate\Event\MigrateRowDeleteEvent instance. If no other module
+   * implements a listener, the \Drupal\migrate_tools\MigrateExecutable listener
+   * (with 1000 weight) does a rollback on the item by default. Any other
+   * listener (with lower weight) might take another action (think un-publishing
+   * a node) and want to call $event->stopPropagation() to prevent the rollback.

This is basic event 101. Let's just remove the comment entirely? That solves the dilemma.

Fixing #5 on commit.