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.

Folders matching with react-18next does not work anymore

See original GitHub issue

Describe the bug Hello,

Since 2.1.6 every translations using the character ‘:’ for folders are nowhere to be found in the extension but the tree is correctly generated.

In the screenshot below you can see ‘pages:tasks:creationMessage’ not being recognized in vsCode but it exist in the tree.

Is it a bug or is it my configuration the problem?

Thanks a lot 😉

Extension Version 2.2.7

Framework/i18n package you are using react, i18next

To Reproduce Here is the config

  "i18n-ally.pathMatcher": "{locale}/{namespaces}.{ext}",
  "i18n-ally.namespace": true,
  "i18n-ally.displayLanguage": "fr-FR",
  "i18n-ally.sortKeys": true,
  "i18n-ally.enabledParsers": ["json"],
  "i18n-ally.keystyle": "nested",
  "i18n-ally.enabledFrameworks": ["react", "i18next"],
  "i18n-ally.extract.targetPickingStrategy": "most-similar",

Device Infomation

OS: Mac OS
Version: Catalina
VS Code Version: 1.46.1

Screenshots

i18n-ally infos: Capture d’écran 2020-06-29 à 11 19 41

Here the folder structure: Capture d’écran 2020-06-29 à 14 00 19

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

Frumbacommented, Jul 15, 2020

Thanks a lot for solving my problem 😉

I’m having a new error though:

Here is my config:

  "i18n-ally.pathMatcher": "{locale}/{namespaces}.{ext}",
  "i18n-ally.namespace": true,
  "i18n-ally.displayLanguage": "fr-FR",
  "i18n-ally.sortKeys": true,
  "i18n-ally.enabledFrameworks": ["react", "i18next"],

1reaction

Frumbacommented, Jul 13, 2020

Yes exactly with i18next they use : for folders and . for inside json access 😄