-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
Refine FastTrack behavior on edge cases #4595
Comments
@teolemon Perhaps we could just let the server tell us something like "nutriscore: not applicable for that category" (we already know that), detect that and not display the fast-track in those cases. |
@teolemon That goes even beyond the fast track button: looks what happens if you click on a "not applicable nutriscore" button... A possible solution at the Smoothie level would be to make the nutriscore button not clickable (and have no forward arrow) if the nutriscore is "not applicable", but that would prevent users from getting info about why the nutriscore is not applicable (the explanation is not available from the server anyway for the moment).
|
What is implemented in #4599: we don't display the fast-track button if the nutriscore or the ecoscore are computed as "not applicable" by the server. Are there be other typical cases to take care of beyond those "not applicable" scores? |
|
What
Which products
Alcohol
Part of
Screenshot/Mockup/Before-After
The text was updated successfully, but these errors were encountered: