Issue with i18n.date and i18n.number in Lingui v3.x #1086
Replies: 1 comment
-
Hello @olajide1234 nice to see that you're trying to migrate to v3 branch, and I'm happy to help. Could you create a repo with next-js, and something similar to your setup where i can reproduce the issue? Not too much free time with Rematch, writing a book, maintaining Lingui, my daily work, etc... hehe |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi. I'm working on migrating our project to Lingui v3.x, but I have an issue with i18n.date and i18n.number. i18n.date basically does not format the date but returns something like
value,date,date0
.It's probably an issue with our project, because when I create a minimal code sandbox, i18n works fine. I think @semoal has reported something similar with a server-side rendered app, but did not disclose the cause. Our app is not server-side rendered.
Here is an example use case for us:
By the way, if I create a reference to the date function e.g. i18n.MyOwnDateRef = i18n.date; and then use
i18n.MyOwnDateRef
in our app; that works fine.I'ld be glad to get any suggestions.
Beta Was this translation helpful? Give feedback.
All reactions