angular-fullstack/generator-angular-fullstack

request feature: add internationalization(i18n) support on server and client side

Open

#571 opened on Sep 20, 2014

View on GitHub
 (17 comments) (0 reactions) (0 assignees)JavaScript (6,134 stars) (1,268 forks)batch import
Help Wantedenhancementmajor

Description

Right now I'm struggling with this approach. I want to know what are thought about this approach from contributors and users that know something about it. Or I'll take other better suggestions about implementing i18n support in Angular and Node + Express engine.

Contributor guide

Tech stack
javascriptangularnodejsexpress
Domain
frontendbackendinternationalization
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
AngularNode.jsExpressi18n concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
This issue is a feature request and open discussion. The author references a specific i18n library approach. To move forward, the scope and acceptance criteria need to be clarified with maintainers. Potential files to explore include the server and client generation templates in the repository, and consider integrating libraries like i18next or angular translate. The existing comments may provide additional context.