Right now, the Migration plugin does a lot of grunt work related to instantiating and managing source, destination, and ID map plugins and their configuration. This is a shame, because core already has an API for abstracting and encapsulating that kind of thing -- namely, plugin collections. The Migration plugin should use this plumbing, rather than reinventing the wheel. It's considered good practice to use plugin collections, and it's nice to delegate as much of the details of plugin management as we can.
↧