This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
Improve vue-i18n example #19
Open
Conversation
This file contains 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem
When running the
vue-i18nexample, and switching the browser to korean using this command (on Linux):The translations from
vue-i18nare still in english, although "vanilla" translation are in korean:Solution
Give the locale to
vue-i18nini18n.tsworks fine.Additional info
Using
as anyformessagesisn't friendly with recommended Typescript eslint rules, switching toas Record<I18nLocales, I18nSchema>is more accurate.Thanks for your work!