Closed (fixed)
Project:
Drupal core
Version:
8.2.x-dev
Component:
migration system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
11 Feb 2016 at 03:37 UTC
Updated:
7 Apr 2016 at 12:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
benjy commentedComment #4
alexpottThis is not going to be pretty because
\Drupalis letting us get away with Drupal\migrate\Plugin\MigrationDeriverTraitComment #5
alexpottI don't think this needs a specific mention in the release notes
Comment #6
alexpottHere's a first effort.
Comment #8
alexpottComment #9
benjy commentedNice work, I can tell this wouldn't have come together so easily.
I don't know about this going on the plugin manager, maybe we could put it in the trait until we solve the root of the issue? #2543552: Modernize migration source plugins Or, maybe we should call it createStubMigration()?
Comment #10
alexpottI think it is natural that the migration plugin manager creates migrations - so why not put it there? Patch attached changes the name to your suggestion and also refactors the method to be simpler and less vulnerable to code changes.
Comment #11
benjy commentedCan we inject the key value service as well.
So much better! alexpott++
Comment #12
alexpottComment #13
alexpott@benjy the reason I didn't inject state yet was because the need to inject the factory not each service - inject factories feels wrong... I'd rather have a MigrationState service or something that offers methods to access all the different migration state collections.
Comment #14
benjy commentedOK, that works for me.
Comment #15
catchPatch looks like a good step forward. I wanted to see if there were any other \Drupal:: calls to be removed, but couldn't find anything that should hold this going in.
Needs a re-roll after the change to Kernel tests - several hunks no longer apply.
Comment #16
alexpottRerolled.
Comment #17
benjy commentedLooks good.
Comment #19
catchCommitted/pushed to 8.2.x and cherry-picked to 8.1.x. Thanks!