headbank → created an issue.
headbank → created an issue.
Just to be clear, do you still expect the migrations to be those generated by migrate_upgrade, or do you look to broaden the scope?
If you restrict to migrate_upgrade's migrations, then I would suggest that the naming not be entirely freeform, as a way of soft-enforcing this (it would be sensible to make that point clear in README.md as well). The drush command allows to specify a prefix ("upgrade_" is the default) so that could be the same setting you offer, while requiring the rest of the ID to match.
As a matter of fact, the issue you've just added is the same I was thinking about raising just yesterday! I'll comment there.
I'm not schooled in contributing (beyond commenting) on issues here but I'll do my best as I've found your tutorial series (through which I discovered this module) very helpful.
Although migrate_upgrade is not a runtime dependency, you do depend on specific migration configs generated by it, so documentation should make this clear.
LOL, and what would be the response time on the new one?
No worries chief, I already took the hint about 9 years and 6 months ago. All the best ;)
Hi @Shreya_th,
The fix is perfect. Thanks!
headbank → created an issue.