-
Notifications
You must be signed in to change notification settings - Fork 773
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
API Errors not localized #1285
Comments
Can I get assigned to this. |
Thanks @Musyonchez, assigned the issue to you. |
Greetings @deepakprabhakara, Can I pick this up ? I can see that @Musyonchez has an open PR with pending work and is not working on it anymore. |
Hi @deepakprabhakara , I looking for my first open source contribution. |
Apologies for the delay in getting to this, @SharmaPrakhar25 please pick this up. Many thanks. |
Hi @deepakprabhakara , in this issue we only need to call t function for errors, right? |
Hello, guys!
Thank you for putting in such effort into the template codebase; the thing seems amazing.
I have a localization-related question. Upon my initial examination of the codebase, I noticed that API errors aren't localized and are always returned in plain English.
For example, in the file pages/auth/forgot-password.tsx:
While the success message is being translated, the API error is being passed as is.
Is this intentional or left for the future? Maybe I'm missing something?
The text was updated successfully, but these errors were encountered: