[Feature] Product History/Revisions Tab & Search Filter

[roshinit-a]

Related Epic

This issue is part of the "Power User Script" Epic: #657

What

I would like to implement the History Tab for product pages. Currently, the new explorer does not have a dedicated tab to view a product's edit history (unlike the old world.openfoodfacts.org/cgi/product_revisions.pl site).

This feature will:

1. Build a new History.svelte (or Revisions.svelte) component to fetch and display the revision history of a product.
2. Integrate this component as a new tab on the product page (e.g., alongside the current Data Sources / Folksonomy tabs).
3. Include the quick-filter / search bar mentioned in Features from the Power User Script #657, allowing users to instantly filter the edit history by contributor username or comment payload.

How

• Add a new section/tab on the products/[barcode]/+page.svelte layout.
• The search functionality will be an instant client-side filter (Svelte reactivity) over the fetched history data array, ensuring a fast, power-user friendly experience without causing extra API load.

Question for Maintainers (@VaiTon, @teolemon)

Before I begin implementation, could you confirm the correct API endpoint to use in the new explorer to fetch a product's revision history?
I'm reviewing the API v2/v3 documentation, but I want to ensure I pull from the exact endpoint you prefer for the new explorer architecture (e.g., is there a specific /api/vX/product/{barcode}/revisions route I should use?).

Please let me know if this plan looks good to go!

[itschetna]

Hi! I’m Chetna, a frontend developer interested in contributing to the explorer.
This feature looks really interesting, especially the UI and filtering part.
I’d love to work on the History tab component.
I’m currently getting familiar with the codebase, so could you guide me on whether I can start with the UI and basic structure first? 😊

[VaiTon]

I'm reviewing the API v2/v3 documentation, but I want to ensure I pull from the exact endpoint you prefer for the new explorer architecture (e.g., is there a specific /api/vX/product/{barcode}/revisions route I should use?).

I don't think we expose an endpoint for the history. It was a feature I requested some time ago but I can't find anything related right now. We have and endpoint to get the last_updated time of each field, AFAIR it was something like ?blame=1.