Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
migration system
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
12 Oct 2015 at 18:09 UTC
Updated:
27 Oct 2015 at 21:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
phenaproximaTry these on for size.
Comment #3
neclimdulConcept looks good!
Nit, tests that don't assert anything are "risky." We can assert that a field doesn't exist or something to ensure things ran quietly but the value didn't make it.
Comment #5
phenaproximaAdded a couple of assertions.
Comment #6
neclimdulThanks
Comment #8
webchickI... could not make any heads or tails out of this issue at all. ;)
Adam explained that the problem is if Article node type migration fails, and a field attempts to be migrated later, exceptions ensue. This makes the code more defensive and avoids errors. Makes sense to me.
Since these changes are self-contained against an experimental module, I believe that makes this eligible for commit during RC. Tagging.
Committed and pushed to 8.0.x. Thanks!
Comment #10
neclimdulThat pretty much sums it up. Its also a step toward allowing content types to be skipped, or possibly renamed. Just pulling an example out of thin air that surely doesn't apply to me, if you where migrating node profiles onto user fields and didn't want to pull over the profile nodes.