Compatibility score doesn't always respect user food preferences

[tclementdev]

I know this is not strictly a mobile thing but I'm adding this here so this lives somewhere and is not lost.

The problem I'm seeing with the way the compatibility score is currently calculated is that it can reach an excellent grade (for example 78%) for an average nutriscore C product when the user food preferences for nutriscore is set to "very important" or even "mandatory". I would expect nutriscore C to produce a lower compatibility score, regardless of other criteria (eco, nova, etc...) being met.

Basically I would expect any unmet criteria dimmed "very important" or "mandatory" to limit how good the compatibility score can be.

As a user I'm finding that I need to tune down the other criteria (eco, nova, additives, etc...) to "not important" in order to prevent compatibility scores from sky rocketing for some products (which otherwise do not have a very good nutriscore). I don't think this makes sense, these other criteria shouldn't make a low nutriscore product have a good compatibility score (unless of course I have set the nutriscore food preferences to "not important").

[g123k]

@tclementdev I close the issue here.
Please continue the discussion on the server repo 👍