mikhael28/paretOS

Bug: AWS Amplify I18N displays the variable name of the phrase if that phrase doesn't exist for the given language

Open

#245 opened on May 14, 2022

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)JavaScript (45 forks)auto 404
Amplifybuggood first issuehelp wantedinternationalization

Repository metrics

Stars
 (35 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

The project has various language translations available. Currently, if a phrase does not exist in the given language's dictionary, I18n returns the variable name for the phrase. It feels like there should be a way to set a default language and have I18n default to that language if a translation does not yet exist for the given language. Maybe in the I18n config options? (I'm not too familiar with the package and haven't had a chance to look at the documentation yet.)

Steps to Reproduce

  1. Go to Create Sprint Template
  2. Change to a language other than English. You'll notice that some of the text is just variable names.

Expected behavior: The English version of the phrase or word appears if the phrase or word does not exist in the current language's dictionary.

Actual behavior: The property name of the phrase or word appears instead.

Reproduces how often: Always

Contributor guide

Research direction
Check the AWS Amplify I18n configuration documentation to see if a fallback language setting exists. If not, implement a fallback mechanism that returns the English translation when the key is missing in the current language. Update the I18n configuration or the translation lookup function accordingly.
Tech stack
javascript
Domain
frontend
Issue type
Bug
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70