i18nAlly support

[mkbctrl]

Hey,

did anyone successfully setup the VScode i18n Ally extension to work with next-translate?
Usually it does work out of the box, the only thing that I frequently change is the path to locale files. In next-translate case I am unable to make it work.

I have the latest version of both VScode (1.70.2) and the extension (2.8.1).

Here's my example component:

locales file auth.json:

{
  "header": {
    "title": "Create Your Free Account",
    "subTitle": "Already have an account?",
    "link": "Sign in"
  },
  "divider": { "text": "or" },
  "policy": {
    "text": "By signing up you agree to our",
    "link": "privacy policy"
  }
}

The settings I changed are the following:

 "i18n-ally.localesPaths": ["locales"],
  "i18n-ally.extract.keyPrefix": "{fileName}", // so I assume when I type: "header.title" the extension should make it "auth.header.title" or am I dumb?

folder structure:

config:

{
  "locales": ["en"],
  "defaultLocale": "en",
  "pages": {
    "/auth/sign-up": ["auth"]
  }
}

Anyone had any issues with that extension in the past? Did I miss smth?

The only case when the autocompletion works is when I type the full path:

Screen.Recording.2022-08-26.at.13.43.30.mov

but it doesn't render the text but the string path (auth.header.link) in my frontend app...

[aralroca]

This is not supported but would be interesting to do it in the feature

[cassus]

See related issue:

• i18nAlly support #983