Problem/Motivation
Discovered by @huzooka! We wrote this together 🤓
Shouldn't \Drupal\migrate\MigrateSkipRowException extend \Drupal\migrate\MigrateException?
Currently, both extend \Exception.
Consequently, the PHPDoc for \Drupal\migrate\MigrateExecutableInterface::processRow(), which says
* @throws \Drupal\migrate\MigrateException
seems wrong, because while rows are being processed by that method, MigrateSkipRowException could be thrown, and MigrateExecutable::processRow() does not catch these.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Comments
Comment #5
mikelutzNo, but it should be added to the throws tag, but we are trying to deprecated MigrateSkipRowException entirely, so I'm going to mark this as a won't fix.