Integrate Nutri-Patrol at various relevant places in the app (tracker)

[teolemon]

What

• Integrate Nutri-Patrol at various relevant places in the app (tracker)

Blocked on

• Document flagging nutripatrol-frontend#58
• Coordinate with the server to integrate the new moderation experience openfoodfacts-dart#885

Scopes

• Extend the scope of Nutri-Patrol (tracker) nutripatrol#59

Where

• Photo manager
• Price Proof manager
• Editing form
• Product page
• Search results

Why

• Moderation of content

Part of

• 🎯 What can I work on ? #525

[teolemon]

@g123k @monsieurtanuki NutriPatrol is now live in production

Tickets only available to moderators
Flagging available to everyone (logged-in)
Flagging webviews by Valentin:
A product https://nutripatrol.openfoodfacts.org/flag/product?barcode=3017620422003&source=web&flavor=off
A image https://nutripatrol.openfoodfacts.org/flag/image?barcode=3017620422003&source=web&flavor=off&image_id=1

We can do it in two times, integrate as links to webviews, then integrate natively at a later point. All the more that integrations need to be done at several places, and that's some work: #5390

[g123k]

I have already discussed this with Valentin and it would be nice to let him implement it (and give him some help).

[Valimp]

Could you asign me on this issue please ?

[teolemon]

• The code has been deployed: feat: nutripatrol product report openfoodfacts-server#10991
• There are server side issues: https://world.openfoodfacts.org/product/4607074063892 eg the // on the url for Report this product to our moderators https://nutripatrol.openfoodfacts.org//flag/product/?barcode=4607074063892&source=web&flavor=off
• There's a new smoothie action that needs to be implemented for the Knowledge panel to work (see the tt.json file in the pull request above)
• I'm not sure whether @alexgarel out of an abondance of caution hasn't put it behind a url flag
• @Valimp @g123k

[alexgarel]

At the moment the NutriPatrol knowledge panel is not displayed for mobile. Ask for display as soon as the action is implemented in the mobile app. (it's to avoid to have an action that does nothing and can be frustrating for the users).

Maybe the mobile app itself should just not display actions knowledge panels it does not support (so that for users with older version they do not get confused) ?