- Issue created by @m.stenta
- 🇺🇸United States m.stenta
Decide if
MigrateBatchExecutable
needs to be restored.It may be that the benefits of removing
MigrateBatchExecutable
(less to maintain and keep in sync withmigrate_tools
) are enough to justify not restoring it, and the issues caused by its removal can be fixed in other ways.We will probably work around this issue in farmOS in the short term, but adding our own explicit call to
\Drupal::messenger()->addMessage()
. The only concern I have is thatmigrate_source_ui
will restoreMigrateBatchExecutable
in a subsequent release and then we'll have *double* messages. It would be good to coordinate to avoid that. - heddn Nicaragua
Can we post some code here on what we'd expect to see from 🐛 MigrateBatchExecutable ignores custom message interface in batch operations Active ?
- First commit to issue fork.
- 🇯🇵Japan eleonel Itoshima 🇯🇵
I opened pull request with the necessary change on this module to work with the patch from https://www.drupal.org/project/migrate_tools/issues/3541864 🐛 MigrateBatchExecutable ignores custom message interface in batch operations Active
- Merge request !12Issue #3507162: StubMigrationMessage no longer used in MigrateBatchExecutable → (Open) created by eleonel