diegohaz/rest

multi-language support

Open

#31 opened on Oct 24, 2016

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (304 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (1,810 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently response strings are hardcoded, so creating a project for non-English users requires to carefully search and replace all user facing text.

At least having all text strings centralized in a single location would make this task much easier and less error prone.

Side note: Let me know what is the best way for me to contribute with suggestions like this. Maybe a Product Pains page would be a better option as not to clutter the issues page with these enhancement requests.

Contributor guide

Research direction
Implement internationalization (i18n) by extracting all hardcoded strings into a centralized JSON file (e.g., en.json) and loading them based on a locale setting. Use a library like i18n node or simple custom logic.
Tech stack
javascriptnodejsexpress
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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.
Clear
Prerequisites
Node.jsExpress
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70