-
-
Notifications
You must be signed in to change notification settings - Fork 400
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
When deleting all nutrients, some computed values are kept in DB #10933
Comments
@raphael0202 We chose to have some computed values in the nutriments field, so this behaviour is normal. It is useful in particular for easing the creation of graphs and search filters. We could decide to do it differently in the future. |
But as all nutrient values were deleted, I was expected the computed values to be deleted as well. But it's definitely not a major issue. |
nutrition-score-fr and nutrition-score-fr_100g should definitely be removed, but the other ones are computed from ingredients, so they should stay |
ah in fact it's probably a product where nutriments are estimated, that's why we get nutriscore-score-fr so everything looks normal in this case |
Thank you for the explanations! I'm closing this issue |
When we remove all nutrients from a product using the web version, we still have the following (computed values) in the
nutriments
field:In Robotoff, I added a special case to consider the product nutrients as missing if there are only these keys: openfoodfacts/robotoff@0e4aff3.
The text was updated successfully, but these errors were encountered: