Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add extraction support to react-i18next framework #951

Conversation

mkevinosullivan
Copy link
Contributor

@mkevinosullivan mkevinosullivan commented Jun 22, 2023

This commit adds the supportAutoExtraction array of supported formats and the detectHardStrings method from GeneralFramework to the ReactI18nextFramework, to enable hard-coded string extraction without needing the "general" framework to be enabled/loaded in the .vscode/settings.json file.

Now the configuration entry can simply be

{
  "i18n-ally.enabledFrameworks": ["react-i18next"],
}

instead of

{
  "i18n-ally.enabledFrameworks": [
      "react-i18next",
      "general"
    ],
}

Fixes #948

This commit adds the `supportAutoExtraction` array of supported formats
and the `detectHardStrings` method from `GeneralFramework` to enable
hard-coded string extraction for react-i18next framework, without
needing the "general" framework to be enabled/loaded in the
`.vscode/settings.json` file.
@terales
Copy link
Collaborator

terales commented Jul 11, 2023

Merged within #970

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Hard-coded strings feature doesn't work if i18n-ally.enabledFrameworks is explicitly set to a single framework
2 participants