reactioncommerce/reaction

Introduce translatable data fields

Open

#6.497 aberto em 15 de mai. de 2020

Ver no GitHub
 (0 comments) (0 reactions) (0 assignees)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.

Guia do colaborador

Pilha de tecnologia
javascriptreactgraphqlnodejsdockerkubernetes
Domain
full stackbackend
Tipo Issue
feature
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
4
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
over 1 week
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
stale
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
mostly clear
Prerequisites
Familiarity with GraphQLKnowledge of MongoDBUnderstand surcharges pluginBasic i18n concepts
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
25
Direção de pesquisa
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.