Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.If this gets merged; https://www.drupal.org/node/2682585 we're going to need to rename to MigrationConfigurationTrait.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2723535-2.patch | 656 bytes | willwh |
Comments
Comment #2
willwh CreditAttribution: willwh at Drupalize.Me commentedand here's a patch...
Comment #3
dscl CreditAttribution: dscl as a volunteer and at Trellon, LLC, DevBrains commentedIf we assume people will be using the latest core version, we can do it now since that ticket got committed and shipped into 8.1.3.
But changing it would break the module for anyone using a core version < 8.1.3.
And the final patch for that ticket kept the MigrationCreationTrait in and deprecated it, so changing it isn't *immediately* required.
Maybe we can postpone it. Not sure.
Comment #4
mikeryanThere'll be non-BC-maintaining changes coming for 8.2.x (in particular, #2695297: Refactor EntityFile and use process plugins instead) that will affect migrate_upgrade. So, my plan is to have an 8.x-2.0 release which only supports core 8.1.x (and keeps using MigrationCreationTrait), and open a new 8.x-3.x branch to support core 8.2.x and up - this patch will go into that branch. I'm putting off branching until I have to (i.e., when there's a BC breaker like the EntityFile change).
Comment #6
mikeryanNow that we have the 8.2.x-compatible branch, committed - thanks!