Problem/Motivation
It looks like we have all the right composer.json dependencies setup, more or less. We could probably make the version constraint less strict and move migrate_plus into the required section. Why? Because it looks like we now have some event subscribers in this base module that depend on migrate_plus. And we should add migrate_plus to .info.yml file as well.
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #17 | interdiff.txt | 352 bytes | quietone |
| #17 | 2918496-17.patch | 3.63 KB | quietone |
| #14 | interdiff-12-14.txt | 482 bytes | quietone |
| #14 | 2918496-14.patch | 3.98 KB | quietone |
| #12 | migrate_plus-n2918496-12.interdiff.txt | 777 bytes | damienmckenna |
Comments
Comment #2
quietone commentedNeeds to be considered along with the idea of removing the event subscribers.
Comment #3
quietone commentedheddn, Is this still relevant?
Comment #4
heddnI'd have to check. Do we still have event subscribers?
Comment #5
quietone commentedThere are two, MigrateOrder and MigrateProduct, both using onPreRowDelete for handling rollback.
http://cgit.drupalcode.org/commerce_migrate/tree/src/EventSubscriber
Comment #6
quietone commentedHow about a patch that addresses the dependencies of migrate_plus in all modules.
Gathered some information;
Migrate Plus process plugins are used in sub modules Commerce, Magento and Ubercart.
The PrepareRow event is used in sub modules Commerce and Ubercart.
And then made a patch.
I got a little carried away and also modified the composer.json for drupal/core.
This definitely needs a review by someone other than me!
Comment #9
quietone commented'Twas a stray comma
Comment #11
damienmckennaIt might be useful to list migrate_plus in the composer.json file too.
Comment #12
damienmckennaDuh Damien. Sorry.
Comment #14
quietone commented@DamienMcKenna, thanks!
Need a new line.
Patch adding the new line.
Comment #15
heddnShould we standardize on ^4 or ^4.0? One position or 2? I think the difference is non-existent between the two when it comes to a point release of zero and the carrot. See https://getcomposer.org/doc/articles/versions.md.
Comment #16
damienmckennaBecause of the possibility for API changes, I'd suggest sticking to
^x.yrather than^x.Comment #17
quietone commentedAfter reading the composer docs linked to in #15 I think there is no practical difference between ^4 and ^4.0. So then why add it? We can always add x.y later if it is needed. Or have I got that wrong? I did make this patch using just "^4" but happy to change to "^4.0" if it makes a difference.
Comment #19
quietone commentedThanks all!