reactioncommerce/reaction

Introduce translatable data fields

Open

#6 497 ouverte le 15 mai 2020

Voir sur GitHub
 (0 commentaires) (0 réactions) (0 assignés)JavaScript (12 181 stars) (2 198 forks)batch import
enhancementhelp wanted

Description

Prerequisites

  • Are you running the latest version?
  • Are you able to consistently reproduce the issue?
  • Did you search the issue queue for existing issue? Search issues

Issue Description

As discussed on reaction-feature-requests#94, products should have translatable fields for multi-language shops.

Possible Solution

Implement a solution similar to what's done with messagesByLanguage in api-plugin-surcharges.

Guide contributeur

Stack technique
javascriptreactgraphqlnodejsdockerkubernetes
Domaine
full stackbackend
Type d'issue
feature
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
4
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
over 1 week
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
stale
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
Familiarity with GraphQLKnowledge of MongoDBUnderstand surcharges pluginBasic i18n concepts
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
25
Direction de recherche
Begin by studying the `messagesByLanguage` implementation in the `api plugin surcharges` repository to understand the pattern used for translatable fields. Then, inspect the product schema in the Reaction database (likely in the `reaction` repository's imports/custom packages) to identify which fields (e.g., title, description) should be made translatable. Finally, review the GraphQL type definitions for products to determine how to add a new field for translations and update the resolvers accordingly. No linked PRs or comments provide further guidance, so this requires independent exploration.