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
I'd like to put a list that needs to be translated in my reducer instead of in my component. This works fine, however when it comes time to extract these values out of the code, it won't happen because the 't' function is working with an iterator instead of a hardcoded string.
I've seen workarounds in here on how to get the context out of the component and into other parts of the app, is the reccomended way to translate things that exist outside of the component?
The text was updated successfully, but these errors were encountered:
most of the things coming from a database will be pre-translated. I'm more talking about arrays or objects that I may be creating internally. For example, I could hardcode 5 list items in a component, or I could map over them. Another good example would be how to apply translations to components from plugins.
@shankie-san great plugin, I could definitely see a use for this. More than anything though I need a way to wrap 't' function wiht something else besides hardcoded strings.
I'd like to put a list that needs to be translated in my reducer instead of in my component. This works fine, however when it comes time to extract these values out of the code, it won't happen because the 't' function is working with an iterator instead of a hardcoded string.
I've seen workarounds in here on how to get the context out of the component and into other parts of the app, is the reccomended way to translate things that exist outside of the component?
The text was updated successfully, but these errors were encountered: