Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add support for Chrome extension style JSON file

See original GitHub issue

Is your feature related to a specific framework or general for this extension

CHrome Extension JSON format

Is your feature request related to a problem? Please describe.

Accroding to https://developer.chrome.com/extensions/i18n , i18n file for Chrome Extension looks like

{
"msg": { "message": "translate 1", "description": "you should translate it as ..." },
"msg_2": { "message": "translate 2" }
}

It has the shape:

type ChromeExtensionLikeFormat = Record<string, {
    message: string,
    description?: string
}>

Additional context

Current behavior

For longer message

Issue Analytics

State:
Created 4 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

2reactions

antfucommented, Jan 6, 2020

@Jack-Works The chrome extension is supported as a framework. Please update to v0.10.1 and check it out.

Note you may need to do the following things to make it work

remove your custom framework setting
set "i18n-ally.enabledFrameworks": "chrome-ext"

My working config for reference

{
  "i18n-ally.enabledFrameworks": "chrome-ext",
  "i18n-ally.localesPaths": "_locales",
  "i18n-ally.dirStructure": "dir",
  "i18n-ally.keystyle": "nested"
}

1reaction

Jack-Workscommented, Jan 7, 2020

Cool! I’ll try it out! Thank you