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
Is your feature related to a specific framework or general for this extension
react-i18next
Is your feature request related to a problem? Please describe.
The issue that I am experiencing comes into play after passing a custom configuration object to i18next utilizing the resources option. As a result of this, i18n-ally is unable to locate the correct language configuration file.
Here is an example that entails my configuration:
And how I utilise it:
Currently, if I alter 'appDebug' to 'app-debug' as shown below, i18n-ally operates correctly. However, this modification does not correspond with my intended code usage.
Describe the solution you'd like
My suggestion to resolve this issue is to facilitate a namespace(s)Map configuration which includes function support. The function should be able to accept the namespace(s), as extracted by i18n-ally, and subsequently return user-defined namespace(s).
The text was updated successfully, but these errors were encountered:
I have the same requirement, for example, my language. json in src/views/AppHeader, and the data I put in the message will remove the src.views key, but I cannot match it with the plugin
Is your feature related to a specific framework or general for this extension
react-i18next
Is your feature request related to a problem? Please describe.
The issue that I am experiencing comes into play after passing a custom configuration object to i18next utilizing the resources option. As a result of this, i18n-ally is unable to locate the correct language configuration file.
Here is an example that entails my configuration:
And how I utilise it:
Currently, if I alter 'appDebug' to 'app-debug' as shown below, i18n-ally operates correctly. However, this modification does not correspond with my intended code usage.
Describe the solution you'd like
My suggestion to resolve this issue is to facilitate a namespace(s)Map configuration which includes function support. The function should be able to accept the namespace(s), as extracted by i18n-ally, and subsequently return user-defined namespace(s).
The text was updated successfully, but these errors were encountered: