-
|
hi 👋 the i got bitten by this when i noticed my page titles wouldn't dynamically update when using code like this: const { $t } = useFluent();
useTitle($t("loading")); // no error but does not actually work when switching languages … while this works fine: const { $t } = useFluent();
useTitle(() => $t("loading")); // works instantly when switching languagesthis may not be a bug per se because a i'm wondering if there's a design choice behind this which i may not have understood? or maybe i'm just ‘holding it wrong’? in which case, please tell me what i should do differently? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi, The return type of Having
For example, let's say that you want to add site name to your page titles: useTitle(`${$t("loading")}-${site}`); // not reactiveReactive result of useTitle(`${$t("loading").value}-${site}`); // not reactiveSo you are still forced to use useTitle(() => `${$t("loading").value}-${site}`); // reactive, but uglyThat is why we have the current design: useTitle(() => `${$t("loading")}-${site}`); // reactive, and looks fineThe nicest solution would, probably, be a better |
Beta Was this translation helpful? Give feedback.
-
|
thanks, this makes total sense! re. the tighter type to force refs/reactivity, that's indeed useful for internal composables that are always intended to be used a certain way. in my example, VueUse |
Beta Was this translation helpful? Give feedback.
Hi,
The return type of
$tis a string, and yes, it cannot be reactive. But$tmethod itself is reactive, as you found out by using() => $t().Having
$treturnRef<string>would be less convenient, forcing.valueusage everywhere.computed(() => $t('...'))- this is not a workaround, but a normal use case.Most of the time when you are in
script setupyou are already in some kind of computed context, and you can use$tdirectly.For example, let's say that you want to add site name to your page titles:
Reactive result of
$twill not help you in this case:So you are still forc…