We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
We can not create products with nullable customFields. Some of our customFields are optional in version 1.9 but do not work on 2.x.
To Reproduce Steps to reproduce the behavior:
export const ProductCustomFields: CustomFieldConfig[] = [ { name: 'start_date', label: [ { languageCode: LanguageCode.en, value: 'Start date', }, ], type: 'datetime', }, { name: 'useType', type: 'string', nullable: true, label: [ { languageCode: LanguageCode.fr, value: "Type d'utilisation du produit", }, { languageCode: LanguageCode.en, value: 'Use type', }, ], options: [ { value: ProductUseType.EVERYWHERE, label: [ { languageCode: LanguageCode.en, value: 'Usable everywhere', }, ], }, { value: ProductUseType.STORE, label: [ { languageCode: LanguageCode.en, value: 'Usable in store', }, ], }, { value: ProductUseType.ONLINE, label: [ { languageCode: LanguageCode.en, value: 'Usable online', }, ], }, ], }, ]
Variable "$input" got invalid value {} at "input.customFields.start_date"; DateTime cannot represent non string or Date type {}
Even if we set nullable: true in the customFields, there's always an error because the graphql query sends "start_date": {}
nullable: true
"start_date": {}
The custom field "useType" value [""] is invalid. Valid options are ['everywhere', 'offline', 'online']
The graphql query sends "useType": "" but the select is good
"useType": ""
Expected behavior
We would like to have optional customFields with empty value, so we can create products without filling in the fields
Environment (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered:
I tested with the 2.0.7 version. It fixed the datetime problem (start_date example) but not the nullable problem (useType example)
Sorry, something went wrong.
7e2c17a
michaelbromley
No branches or pull requests
Describe the bug
We can not create products with nullable customFields. Some of our customFields are optional in version 1.9 but do not work on 2.x.
To Reproduce
Steps to reproduce the behavior:
Even if we set
nullable: true
in the customFields, there's always an error because the graphql query sends"start_date": {}
The graphql query sends
"useType": ""
but the select is goodExpected behavior
We would like to have optional customFields with empty value, so we can create products without filling in the fields
Environment (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: