You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Overall, I do a quite simple use of Vue i18n, I would say ~80%+ of my code simply uses $t('key'), upgrading to v9/v10/v11 as we went to Vue 3 was not a major issue.
Back to the legacy API,
My understanding is that it will work fine in applications using Vue Options API, just how we interact with Vue i18n will change. is that correct?
Going further, I could not understand if this will simply means some overloads will work differently (like the changes in v10), or if there will be a whole set of functions that will no longer work, or that I will need to update all my components somehow...
A few other things I am assuming:
I can still use the global $t and etc
I don't need to add a setup function to my components calling useI18n (unless I need to customize something)
Switching to legacy: false on my createI18n, I would see the issues if I was still relying on the legacy api.
If I can use my application with legacy: false just fine, can I expect that the removal of the legacy api will have minor/no effect on it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am trying to understand the impact of the deprecation/future removal of Legacy API on my application, from here: https://vue-i18n.intlify.dev/guide/migration/breaking11.html#deprecate-legacy-api-mode
Overall, I do a quite simple use of Vue i18n, I would say ~80%+ of my code simply uses
$t('key'), upgrading to v9/v10/v11 as we went to Vue 3 was not a major issue.Back to the legacy API,
My understanding is that it will work fine in applications using Vue Options API, just how we interact with Vue i18n will change. is that correct?
Going further, I could not understand if this will simply means some overloads will work differently (like the changes in v10), or if there will be a whole set of functions that will no longer work, or that I will need to update all my components somehow...
A few other things I am assuming:
$tand etcsetupfunction to my components callinguseI18n(unless I need to customize something)legacy: falseon mycreateI18n, I would see the issues if I was still relying on the legacy api.If I can use my application with
legacy: falsejust fine, can I expect that the removal of the legacy api will have minor/no effect on it?Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions