[Misc][Refactor] Automate namespace collection for en locale with vite plugin
#4625
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
…to namespace-plugin
…nd extraction of the amespaceMap constant to its own file.
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.
What are the changes the user will see?
n/a
Why am I making these changes?
Experience and sustainability of development
What are the changes from a developer perspective?
Instead of manually adding each new namespace, every namespace added to the "en" locale will be automatically included.
Refreshing the page when changing/deleting/creating any JSON file in
public/localeswhich serves as a micro-optimization.src/plugins/utils-plugin.tsfile, which acts as an intermediary between variables/functions that both plugins (of Vite) and the client can use. By using this file, a server restart is isolated whenever it changes.And some additional documentation.
How to test the changes?
You can observe that after reloading the page (if you modified/created/deleted a namespace), these should be added in camelCase format to the nsEn constant by the development tools in the i18n file.
Checklist
betaas my base branchHave I considered writing automated tests for the issue?If I have text, did I make it translatable and add a key in the English locale file(s)?npm run test)Are the changes visual?Have I provided screenshots/videos of the changes?