How openfoodfacts/nutripatrol-frontend works
Nutri-Patrol is a React moderation frontend for reporting product/image issues and reviewing reported-image tickets. The main user workflow is sign-in, submit a flag to the API, then see confirmation; moderators use the ticket dashboard to inspect reports and update ticket status. The graph also preserves the documented tutorial and flag-information pages. Edges reflect shown calls or README statements; unsampled implementation details and uncertain connections are omitted.
Main entry points: App.tsx App routing · FlagFormPage.tsx Flag form · TicketList.tsx Ticket lists · TicketShow.tsx Ticket detail
Components 25
Application
- App routing
src/App.tsx - Home page
src/pages/HomePage.tsx - Flag guidance
src/pages/FlagInfos.tsx - Moderation tutorial
src/pages/Tutorial.tsx
Flag Reporting
- Flag form
src/pages/FlagFormPage.tsx - Flag choices
src/const/flagsConst.ts - Submission confirmation
src/pages/ThanksPage.tsx - Usage analytics
src/analytics.ts
Ticket Moderation
- Admin dashboard
src/App.tsx - Ticket lists
src/admin/tickets/TicketList.tsx - Reason lists
src/admin/tickets/ReasonTicketList.tsx - Inappropriate tickets
src/admin/tickets/InappropriateTicketList.tsx - Ticket detail
src/admin/tickets/TicketShow.tsx - Report summaries
src/admin/tickets/FlagSummary.tsx - Flag data helpers
src/admin/tickets/flags.ts - Ticket filters
src/admin/tickets/choices.ts - Image preview
src/admin/tickets/TicketThumbnailField.tsx - Ticket actions
src/admin/tickets/TicketActionsField.tsx - API data provider
src/admin/dataProvider.ts
Identity
- Login page
src/pages/LoginPage.tsx - Auth provider
src/admin/authProvider.ts - Development accounts
src/admin/devAuth.ts
Other components
- Contributor or moderator
- Nutri-Patrol API
- Open Food Facts
Connections 28
- Contributor or moderator → App routing: opens frontend
README.md - App routing → Home page: routes to
src/App.tsx - App routing → Flag guidance: routes to
src/App.tsx - App routing → Moderation tutorial: routes to
src/App.tsx - App routing → Flag form: routes to
src/App.tsx - App routing → Submission confirmation: routes to
src/App.tsx - App routing → Admin dashboard: configures
src/App.tsx - Admin dashboard → API data provider: uses
src/App.tsx - Admin dashboard → Auth provider: uses
src/App.tsx - Flag form → Flag choices: uses options
src/pages/FlagFormPage.tsx - Flag form → Nutri-Patrol API: submits flag
src/pages/FlagFormPage.tsx - Flag form → Usage analytics: tracks submission
src/pages/FlagFormPage.tsx - Flag form → Submission confirmation: shows after success
src/pages/FlagFormPage.tsx - API data provider → Nutri-Patrol API: reads and updates tickets
src/admin/dataProvider.ts - Admin dashboard → Ticket lists: renders tickets
src/App.tsx - Admin dashboard → Reason lists: routes to
src/App.tsx - Admin dashboard → Inappropriate tickets: routes to
src/App.tsx - Ticket lists → Ticket filters: uses filters
src/admin/tickets/TicketList.tsx - Ticket lists → Image preview: renders preview
src/admin/tickets/TicketList.tsx - Ticket lists → Ticket actions: renders actions
src/admin/tickets/TicketList.tsx - Ticket detail → Report summaries: renders reports
src/admin/tickets/TicketShow.tsx - Ticket detail → Image preview: renders preview
src/admin/tickets/TicketShow.tsx - Ticket detail → Ticket actions: renders actions
src/admin/tickets/TicketShow.tsx - Report summaries → Flag data helpers: uses flag helpers
src/admin/tickets/FlagSummary.tsx - Reason lists → Ticket lists: uses list
src/admin/tickets/ReasonTicketList.tsx - Login page → Auth provider: checks session
src/pages/LoginPage.tsx - Auth provider → Development accounts: uses dev role
src/admin/authProvider.ts - Login page → Open Food Facts: offers sign-in
README.md