-
Notifications
You must be signed in to change notification settings - Fork 293
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
Support for Namespaces #122
Comments
@feelinwavy Wow, first time to see this syntax! I would love to support it if possible. May I have more information listed below?
Thanks! |
@antfu, I use next-i18next. https://www.npmjs.com/package/next-i18next It would be sooo awesome! |
Thanks. It looks a little complicated to integrate into the current codebase. So it may take a little bit longer. Please keep turned! 😃 UPDATE: Please track the progress on #129 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Awesome extension! This feature would be really appreciated. |
Hello, Im having the same issue trying to use nextI18nNext with i18nAlly extension and the extension its not wokring with |
Any progress? Thanks! |
I have the same issue |
this solution worked with me: |
@hussain7college Does it work with the ":" as a separator for namespace ? |
Does it support colon notation?
How can I get things working when namespace is selected with
:
The text was updated successfully, but these errors were encountered: