kazupon/vue-i18n

Change the way missing translation keys are detected

Open

#563 opened on Apr 16, 2019

View on GitHub
 (14 comments) (10 reactions) (0 assignees)JavaScript (886 forks)batch import
Type: Improvementgood first issue

Repository metrics

Stars
 (7,181 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hello,

Our translations are handled with Crowdin and one particularity with Crowdin is that, if a key wasn't translated yet and we sync them; Crowdin will return the key with an empty string instead of returning the file without the missing keys.

The thing is that, vue-i18n considers the empty string as an already-translated key, so it will uses it instead of fallbacking to the default version (english).

It would be great to override this default rule, so I can say that: "If my key is missing OR my key is empty, fallback to the default version".

An implementation suggestion would be a handler in the config that returns true or false if the key passed should be considered as missing?

Contributor guide

Research direction
Investigate the vue i18n source code to locate where missing key fallback is determined. Propose adding a configuration option (e.g., `missingHandler`) that allows returning a boolean to treat a key as missing. Implement and test the change.
Tech stack
javascriptvue
Domain
frontend
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-3 hours
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
Vue.jsJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70