fix: Nutri-Score for olive oils with unrecognized ingredients

[stephanegigandet]

This PR:

• fixes an issue in Tags.pm for some functions that return a property value. When the property value was 0, it was not returned.
• simplifies and makes it more clear that for some categories we force the % of fruits/vegetables while for some other we provide default values in case we do not have ingredients
• this fixes products like olive oils that have unrecognized ingredients (e.g. an expected way to write that it contains 100% olive oil): we force them to have 100% fruits/vegetables

[alexgarel]

LGTM !

[alexgarel]

Have we any documentation on how this property works ?

[stephanegigandet]

@alexgarel I'm adding a comment for it at the top of the taxonomy, where there is some doc for some properties already.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[aleene]

so the category defines the nutriscore. You can also let it define the ingredient (so you get the right nutriscore?).
This can be extended to all single ingredient categories. Could help as a category quality check as well: if there are more than one ingredient detected, then either the category is wrong or the ingredient.

[stephanegigandet]

so the category defines the nutriscore. You can also let it define the ingredient (so you get the right nutriscore?). This can be extended to all single ingredient categories. Could help as a category quality check as well: if there are more than one ingredient detected, then either the category is wrong or the ingredient.

@aleene We already have a mechanism for that in fact (added by @benbenben2 ),
e.g. for the extra-virgin olive oils category:

<en:Olive oils
en:Extra-virgin olive oils, Extra virgin olive oil
[..]
expected_nutriscore_grade:en:c
expected_ingredients:en: en:olive-oil

[aleene]

Can't you the expected_ingredient field to calculate the nutriscore?