[Feature][ENV] make i18n debugging an optional env setting #2692
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.
What are the changes?
I've made i18n debugging an optional setting that can be changed via
.env
filesWhy am I doing these changes?
It's spamming the console but more importantly adding noise to the test-result output (a huge object in every test)
What did change?
i18n is no longer always in debug mode but can be forced into it by changing
VITE_I18N_DEBUG
to the value1
Screenshots/VideosHow to test the changes?
.env.development
VITE_I18N_DEBUG
to the value1
Checklist
npm run test
)[] Are the changes visual?