Rename the commerce submodule are decided in the parent issue #2961979: Rename migrations and plugins
| Comment | File | Size | Author |
|---|---|---|---|
| #16 | interdiff.txt | 590 bytes | quietone |
| #16 | 2969074-16.patch | 144.94 KB | quietone |
| #14 | 2969074-14.patch | 144.94 KB | quietone |
| #14 | interdiff.txt | 3.14 KB | quietone |
| #12 | interdiff.txt | 930 bytes | quietone |
Comments
Comment #2
quietone commentedFirst go at the changes. Changed everything except for comments.
Comment #4
quietone commentedIncorrect character leftover from a sed command that I cleanup by hand and missed one.
Comment #5
quietone commentedNow update the comments to change references to D7 to Commerce 1 or similar.
Comment #6
quietone commentedall the 'Commerce 1' tags can be changed to Commerce
Comment #7
quietone commentedChange the migration tags.
Comment #8
heddnThere still seems to be some occurrences of 'Commerce 1'. Back to NW.
Do we need to worry about BC? Since we are still in alpha, probably not. Sorry folks, I know this will probably hurt a little.
Comment #9
quietone commentedYes, I didn't do a grep on the module. Thanks for spotting it. I found 2 instances of Commerce 1 in two test files.
Yes, sorry about the change but it will help in the future.
Comment #11
heddnCommerceMigrationProvidersExistTest and 31 other files still mention 'Commerce 1'.
Comment #12
quietone commentedNeeded to start over and reroll the patch in #7. This patch does that and adds the changes made in patch #9, which changes 'Commerce 1' to 'Commerce' for the tags in two tests.
As for the other 31 files, the instance of 'Commerce 1' is in comments which are specific to Commerce 1.
Comment #14
quietone commentedAdding fixes for the latest commits which used the old naming system.
Comment #15
quietone commentedWith this patch grep finds 41 instances of 'Commerce 1' all in comments, which I think is OK. It makes it clear what the code is for and it can be changed as needed when Commerce 2 sources are used. Or am I missing something on this fine day?
Comment #16
quietone commentedAnd let's fix the coding standard error, a removal of an unused use statement.
Comment #17
heddn