-
-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: reactive availableLocales
using computed property
#2058
feat: reactive availableLocales
using computed property
#2058
Conversation
}) | ||
expect(i18n.availableLocales).toEqual(['en', 'ja', 'fr'].sort()) | ||
}) | ||
test('reactive update', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is necessary to test with watch
/ watchEffect
to see if the reaction is taking place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your contributing!
I've just reviewed your PR!
Please, let's check it out :)
@intlify/core
@intlify/devtools-types
@intlify/core-base
petite-vue-i18n
@intlify/shared
@intlify/message-compiler
vue-i18n
@intlify/vue-i18n-core
commit: |
hi @kazupon ! i made the new all tests passed |
Just checking, this would be a breaking change right? |
maybe yea |
Thank you for making me realize! v11 branch will be included bug fixes and backward-compatible features until vue-i18n v12 |
resolves #1893
so, I had the same problem and as a solution I implemented the idea suggested by the man who created the issue using
computed
inavailableLocales
atcomposer.ts
also I wrote some tests and change some things in
legacy.ts
to accommodate this of coursenow its works great :)