- Issue created by @xurizaemon
- πΊπΈUnited States m.stenta
We should be careful here to ensure that we don't make the same mistake made in Migrate Tools. If the method signature is changed in such a way that it breaks downstream code using/extending it, then Migrate Source UI MUST increment its major version and properly document this.
That is, unless Migrate Source UI isn't committed to semantic versioning... :-(
Perhaps this would be a good time to switch from 8.x-1.x to a 2.0.x with true semantic versioning.
Let's see what gets committed in π New parameters introduced in MigrateExecutable class constructor Active first ...
- π³πΏNew Zealand xurizaemon Εtepoti, Aotearoa π
Good point Michael. I feel I'm confused now from juggling changes (and git is giving me weird results / not showing changes from upstream?), so I'm going to leave this for tonight. Thanks!
- heddn Nicaragua
The fixes for this were already in the dev branch. I thought I'd released it in a tag, but must have missed it.
https://www.drupal.org/project/migrate_source_ui/releases/8.x-1.3 β