-
-
Notifications
You must be signed in to change notification settings - Fork 302
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
Ingredients and Stores cannot be presented in a list #5887
Comments
For the stores, you can have a look at what's done on the Edit page.
And for the ingredients, you can do the same. |
@teolemon the right request for ingredient, eg for french, is: https://world.openfoodfacts.org/api/v1/product/3451790988677.json?fields=ingredients_tags_fr |
I am currently using ingredientsTextInLanguages, other field 'ingredient' is null Ingredients tag fr is not present in the Product class |
For stores, I am currently using stores. I have an issue with StoresInLanguage ; the english value is currently null (despite stores field beeing filled with english stores data) |
The product class contains nutrition values but not their metrics (kJ, kcal...) Shoudl I do this web call on my view ? or the product class should contain the metrics ? |
This issue is blocking #5814
Ideally, to present values in a list of elements, the values need to be given to the app in a list.
That is not the case for Ingredients and stores.The list values IngredientsTagsInLanguage and storeTagsInLanguage are null.
The list of ingredients and stores are found in a single String
This can be found in the nutella page, but also this butter and this juice : https://world.openfoodfacts.org/product/3451790988677/le-beurre-tendre-doux-elle-vire
https://world.openfoodfacts.org/product/3254691586054/le-bio-pour-toute-la-famille-multifruit-pressade
Here are two solutions : correct the serverside answer to give the elements in a listvalue in the request.
or : adapt the code of the rawdata list to have the Strings be broken down into a list.
Solution 2 is the easiest to do, but will create technical dept.
The text was updated successfully, but these errors were encountered: