Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supports enhanced namespace(s) #1165

Open
fangyang921017 opened this issue Jun 17, 2024 · 1 comment
Open

Supports enhanced namespace(s) #1165

fangyang921017 opened this issue Jun 17, 2024 · 1 comment

Comments

@fangyang921017
Copy link

fangyang921017 commented Jun 17, 2024

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:
image
And how I utilise it:
image
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.
image

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).

@fangyang921017 fangyang921017 changed the title Supports enhanced namespaces Supports enhanced namespace(s) Jun 17, 2024
@ccjr1120
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants