fix: warn only when vueI18n property is set but not found #2468
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
BobbieGoede
force-pushed
the
fix/vue-i18n-warning-when-none-specified
branch
from
3feca8c
to
8162e3b
Compare
BobbieGoede
force-pushed
the
fix/vue-i18n-warning-when-none-specified
branch
from
8162e3b
to
a0dcc1b
Compare
DarthGigi
pushed a commit
to DarthGigi/i18n
that referenced
this pull request
Apr 16, 2024
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.
🔗 Linked issue
#2464
❓ Type of change
📚 Description
Resolves #2464
Changed the vueI18n config resolution to only warn when
vueI18nhas explicitly been set but could not been found. Users seem to confuse the warning with an error or would like to turn it off as they haven't set the property.📝 Checklist