-
-
Notifications
You must be signed in to change notification settings - Fork 48
Open
Labels
Type: FeatureIncludes new featuresIncludes new features
Description
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
.
kaguya3222, andruhon and schiughi
Metadata
Metadata
Assignees
Labels
Type: FeatureIncludes new featuresIncludes new features