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
{{ message }}
This repository has been archived by the owner on May 19, 2022. It is now read-only.
When I set the keyPrefix option for a component and include a different component inside, the keyPrefix of that child component will also be set to the value I choose for the parent component. I think that should not be the case.
Child could be used in multiple places and every time it will have a different prefix set.
I don’t think this is a good approach, because it makes the translations really hard to control.
If you really want to support it, I would suggest allowing a function for the keyPrefix option, which takes the parent prefix and returns the childs’ prefix.
In any case, please default to having no prefix, if the keyPrefix option is not given in a component.
The text was updated successfully, but these errors were encountered:
I see the problem is also there for all other i18nOptions. Maybe there should be a new boolean option passDown, which defines whether the options will be inherited by the children of the current component.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I set the
keyPrefix
option for a component and include a different component inside, thekeyPrefix
of that child component will also be set to the value I choose for the parent component. I think that should not be the case.Child
could be used in multiple places and every time it will have a different prefix set.I don’t think this is a good approach, because it makes the translations really hard to control.
If you really want to support it, I would suggest allowing a function for the
keyPrefix
option, which takes the parent prefix and returns the childs’ prefix.In any case, please default to having no prefix, if the
keyPrefix
option is not given in a component.The text was updated successfully, but these errors were encountered: