Skip to content
New issue

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

Trace allergen incorrectly parsed as ingredient #8967

Closed
danielcavanagh opened this issue Sep 7, 2023 · 0 comments · Fixed by #9265
Closed

Trace allergen incorrectly parsed as ingredient #8967

danielcavanagh opened this issue Sep 7, 2023 · 0 comments · Fixed by #9265
Labels
🐛 bug This is a bug, not a feature request. Traces

Comments

@danielcavanagh
Copy link

What

'May contain other tree nuts' is correctly shown as a trace allergen ('nut'), but is also incorrectly added to the list of ingredients

Using 'May contain tree nuts' (no 'other') avoids the issue

Eg. https://world.openfoodfacts.org/product/9346758004008/hazelnut-chocolate-spread-pana-organic (I have manually removed 'other' for now)

Steps to reproduce the behavior

  1. Edit a product and add 'May contain other tree nuts.'
  2. Check the list of ingredients returned by the API (eg. https://en.openfoodfacts.org/api/v0/product/9346758004008/hazelnut-chocolate-spread-pana-organic)

Expected behavior

'Tree nuts' should be registered as a trace allergen only. It shouldn't be registered as an ingredient

Why

It affects ingredient percentages. Trace allergens should never be an ingredient

Type of device

  • REST-API

Number of products impacted

Minimal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug This is a bug, not a feature request. Traces
Projects
Development

Successfully merging a pull request may close this issue.

2 participants