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

Support Component based localization #134

Open
jessie-codes opened this issue Nov 17, 2020 · 0 comments
Open

Support Component based localization #134

jessie-codes opened this issue Nov 17, 2020 · 0 comments
Labels
Type: Feature Includes new features

Comments

@jessie-codes
Copy link

Tell us about your environment

  • **ESLint version:**6.7.2
  • eslint-plugin-vue version: 6.2.2
  • eslint-plugin-vue-i18n version: 0.9.0
  • Node version: 10.16.3

The problem you want to solve.

I want to use Component based localization, which allows for specifying the messages for each country code within the component itself so it's easier to keep track of which component is using which translations. However; since there is no way to configure this to look for translation keys within the components, I can't use the @intlify/vue-i18n/no-missing-keys rule without it throwing warnings.

Your take on the correct solution to problem.

By default, it should look at the components to see if there are any translation keys specified in either messages or sharedMessages.

@ota-meshi ota-meshi added the Type: Feature Includes new features label Nov 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Includes new features
Projects
None yet
Development

No branches or pull requests

2 participants