Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
migration system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
25 Nov 2013 at 07:52 UTC
Updated:
29 Jul 2014 at 23:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
chx commentedBTW thanks for committing #2132441: run-tests.sh --module is broken makes my life quite a bit easier.
Comment #2
chx commentedNote that we have our first config entity migration which I will submit the moment this is in and we have rapidly expanding testing for the Sql and MigrateExecutable classes and... aaaaargh it's going to be very hard to keep up with the pace we have, I wonder how the VDC team did this.
Comment #3
chx commentedComment #4
dawehnerThis comment feels so dirty.
Just wonder why we use 4 spaces instead of 2 spaces everywhere else.
Comment #5
bdone commentedhopefully less dirty
Comment #6
chx commentedBecause
protected $indentation = 4;in Symfony Yaml Dumper. Reconfiguring migrate to use two spaces is doable but an entirely different issue than moving files around.
Comment #7
chx commentedbdone prodded me enough that the sandbox now has spaces reconfigured but it's still a different issue.
Comment #8
larowlanLooks good, changing the indents will break the clean renames and can be tackled in bulk elsewhere.
Comment #9
alexpottWill the new migrate_drupal module also contain the Drupal 7 and 8 etc... migration classes?
Comment #10
chx commentedYes for D7. As for D8 sources, who knows. We need to discuss that. I suspect yes but I am not entirely sure.
D8 destinations, no, that's part of migration, while theoretically you can migrate into anything most people will want to migrate into D8 and so we will keep the D8 destinations in migrate.
Comment #11
catchSorry files in #6 are hidden, so is #5 or #6 RTBC?
Comment #12
alexpott#3 contains the rtbc patch #5 changed the spacing of some yaml files that was out of scope.
Comment #13
catchCommitted/pushed to 8.x, thanks!
Comment #14
chx commented