add useI18n composable #328
Merged
+92
−4
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Haberkamp
force-pushed
the
add-custom-localization
branch
from
dd51e31
to
d76b47e
Compare
alastair-simon
approved these changes
Oct 2, 2024
commit: |
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?
I added a custom built
useI18ncomposable for translating text.Why?
Right now apps are forced to install the i18n plugin and configure it by themselves.
How?
I added a new useI18n hook that will be used by the components. You can toggle the locale by setting the
localeprop on themt-theme-providercomponent.Testing?
I've written some unit tests that make sure the composable works as intended.
Anything Else?