File Affected: collective.easyform.migration.actions
During property mapping in the generation of action models, the property xinfo_headers should use append_list_node instead of append_node.
Expected Behavior:
The current implementation appears to handle it as:
<xinfo_headers>
<element>HTTP_X_FORWARDED_FOR</element>
</xinfo_headers>
Current Behavior:
The XML definition for xinfo_headers is generated from the migration script as:
<xinfo_headers>
HTTP_X_FORWARDED_FOR
</xinfo_headers>
Since this is a list-based property (with <element> nodes), append_list_node should be used instead of append_node for correct parsing.
File Affected: collective.easyform.migration.actions
During property mapping in the generation of action models, the property
xinfo_headersshould useappend_list_nodeinstead ofappend_node.Expected Behavior:
The current implementation appears to handle it as:
Current Behavior:
The XML definition for
xinfo_headersis generated from the migration script as:Since this is a list-based property (with
<element>nodes),append_list_nodeshould be used instead ofappend_nodefor correct parsing.