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
The usual behaviour for "tags" fields such as categories, labels, countries, allergens etc. is that values supplied by producers are added to any existing value entered by users (e.g. producers might sent us only the "Organic" label while we may have more precise labels and mentions such as "AB Organic" or "Rich in fiber").
For allergens and traces though, if the producer sends a value, we can assume that the value is complete, and that it can replace entirely any pre-existing value.
We need to do 2 things:
On the pro platform, when importing allergens and traces, if the producers supplies a value (non empty), then we replace existing values.
When exporting data from the pro platform and importing it to the public platform, if there is a non empty value for allergens, we replace existing values.
Related code:
probably in lib/ProductOpener/Import.pm
there are test files t/integration/import_csv_file.t
fields that should be protected should be configured in Config_off.pm, at the beginning it will be allergens and traces, but we might add other fields later.
The usual behaviour for "tags" fields such as categories, labels, countries, allergens etc. is that values supplied by producers are added to any existing value entered by users (e.g. producers might sent us only the "Organic" label while we may have more precise labels and mentions such as "AB Organic" or "Rich in fiber").
For allergens and traces though, if the producer sends a value, we can assume that the value is complete, and that it can replace entirely any pre-existing value.
We need to do 2 things:
Related to #7850
Part of
The text was updated successfully, but these errors were encountered: