fb6740f333
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 2m55s
Avant : getDisplaySource(term, 'en') lisait term.translations.en (qui n'existe pas) puis fallback sur term.source = francais. C'est ce qui affichait du francais et du néerlandais au mauvais endroit. Apres : le mapping reflete la structure reelle des donnees : - FR (lang='fr') → term.source - EN (lang='en') → term.target - autres (de, es, it, pt, nl, ru, ja, ko, zh, ar, fa) → term.translations[lang] - si manquant → '' (placeholder, JAMAIS une autre langue en fallback) Memes regles pour getDisplayTarget, inversees (defaut = target). Edition (handleTermChange) ecrit au bon endroit : - FR → term.source - EN (ou multi) → term.target - autres → translations[lang] Le remap automatique de term.target au changement de targetLanguage est supprime (lecture a la volee maintenant, plus besoin de modifier l'etat des termes). Aucun changement de donnees, aucun changement backend, aucun changement de schema. Fix purement frontend.
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.