chore: introduce eslint-plugin-vue-i18n #222
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for learn-nuxt-com ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deployed learn-nuxt-com
|
ubugeeei
force-pushed
the
install-eslint-plugin-vue-i18n
branch
from
faa9ec0 to
c1686da
Compare
ubugeeei
force-pushed
the
install-eslint-plugin-vue-i18n
branch
from
c1686da to
48f1ff2
Compare
ubugeeei
force-pushed
the
install-eslint-plugin-vue-i18n
branch
from
48f1ff2 to
e9bd837
Compare
ubugeeei
changed the title
ubugeeei
changed the title
ubugeeei
changed the title
ubugeeei
added
enhancement
yuki-mina
approved these changes
Apr 11, 2025
yuki-mina
reviewed
Apr 11, 2025
antfu
approved these changes
Apr 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi dear @antfu,
I believe we recently added i18n support in #217, and there's actually an amazing linter specifically for that purpose.
https://github.com/intlify/eslint-plugin-vue-i18n
This linter can catch raw text in templates as well as missing message keys.
I went ahead and tried introducing it, and while it caught some raw text issues, what do you think about going ahead and fixing those?If so, I’m happy to help with the work — but if you’d prefer to cover this again on a livestream, then consider this just a suggestion and I’ll leave it to you!