You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When doing a CSV import e.g. during an e2e test custom fields are not being imported correctly if they are not translatable. The customFields are being exported to the translated entity instead.
The linked message is not related to the CSV import. There is also a pretty obvious fix I could create a PR for. Just wanted to create an issue before creating a Pull Request because this is how it's described in CONTRIBUTING.md.
Describe the bug
When doing a CSV import e.g. during an e2e test custom fields are not being imported correctly if they are not translatable. The customFields are being exported to the translated entity instead.
Check: https://github.com/vendure-ecommerce/vendure/blob/master/packages/core/src/data-import/providers/import-parser/import-parser.ts#L401C20-L401C50
parsedCustomFields
is being created and stored in the translation.customFields
are never being assigned toparsedProduct
.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The field should be populated from the CSV file
Environment (please complete the following information):
Additional context
I'd gladly create a PR for this issue.
The text was updated successfully, but these errors were encountered: