appbaseio/reactivesearch

Support translations for component's static-text

Open

#173 opened on Jan 3, 2018

View on GitHubContributor guide
 (2 comments) (3 reactions) (0 assignees)JavaScript (487 forks)batch import
enhancementhacktoberfest

Repository metrics

Stars
 (4,835 stars)
PR merge metrics
 (Avg merge 3d 7h) (1 merged PR in 30d)

Description

Issue Type:

Enhancement

Description:

Static text displayed by the components should have i18n support.

Example spec can be:

<Component
   translation:{{
     "textRef": "translated value",
     ...
   }}
/>

The spec format is similar to how we support innerClass prop. To improve consistency, we can perhaps use the same key values for the possible translatable text values as we use for the innerClass prop.

Contributor guide

Research direction
Examine the innerClass prop implementation as a pattern. Look for existing i18n utilities or libraries used in the codebase and propose a translation prop similar to the example.
Tech stack
javascriptreact
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Reacti18n
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60