Problem/Motivation
When the extract plugin fails to find the requested array element, it fails and logs the following message to the message table:
Array index missing, extraction failed.
Similarly, if the source value passed to the plugin is not an array, then the plugin fails with this message:
Input should be an array.
The message table identifies which row caused the problem, but does not show which field is being processed. A typical migration may handle dozens of fields, with many calls to the extract plugin. It would be helpful to know which field is being processed when the error occurs.
Proposed resolution
Include the destination property in the saved message.
In the first case, suggest adding a default option.
Remaining tasks
User interface changes
None
If #3063856: Expose full set of debugging data in migrate_message table (filterable/searchable) lands, then the improved error messages will be visible in the UI.
API changes
None
Data model changes
None