Enums in IngredientsAnalysisTags.dart don't have the 'unknown' element about openfoodfacts-dart HOT 3 CLOSED

I understand your thoughts, if the api specifies it as unknown, it would be logical to write it in the enums as well, but does it make such a big difference that it is worth changing it?

Or do you mean that we should use maybe and unknown

from openfoodfacts-dart.

There should be both maybe and unknown elements.
For example: enum VeganStatus { IS_VEGAN, IS_NOT_VEGAN, MAYBE, UNKNOWN }

The difference between maybe and unknown could be significant for some kinds of applications. For example:

• When a product has unknown vegan status, that means that 1+ of its ingredients have unknown vegan status - such ingredients either are not in the ingredients.txt file yet, or their vegan status there is not specified yet.
• When a product has maybe vegan status, that means that 1+ of its ingredients have maybe vegan status - such ingredients are present in the ingredients.txt file and their vegan status is explicitly specified as maybe (or is inherited from parent ingredient type), which means that they could be both vegan and non-vegan, the actual status depends on how the ingredient from a concrete product was manufactured.

from openfoodfacts-dart.

I agree, we should have both "maybe" and "unknown".

from openfoodfacts-dart.