Closed (fixed)
Project:
Feeds
Version:
8.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Dec 2018 at 16:57 UTC
Updated:
3 Jan 2019 at 14:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
megachrizThanks for reporting. I think reverting #2997951: Custom mapping source should use value as item getter instead of machine name? could have fixed this issue. To ensure that, we need to add test coverage for this issue.
I start with forcing tests to pass machine names to the method
::createFeedTypeForCsv().Comment #4
megachrizThis adds a test for importing a CSV with spaces, uppercase characters and special characters in the column names. I think I've fixed the test failure for #2 too.
Comment #6
megachrizYay! The test passes. Now we have test coverage for the bug reported in this issue!
Committed #4.
Comment #7
megachrizSpoke too soon, #2997951-9: Custom mapping source should use value as item getter instead of machine name? - which introduced the bug reported in this issue - still passes.
The changed test also tests updating items. I forgot that the issue reported here was specifically to do with updating existing items. I also added a test for altering parsed CSV data. This would cover the case that broke Feeds Tamper.
I now ensured that the changes in these test don't pass with #2997951-9: Custom mapping source should use value as item getter instead of machine name? applied.
Comment #9
megachrizCommitted #7.