Closed oyeanuj closed 6 years ago
For anyone else, who might come across this in the future, here is where I ended up:
So, there have been a few discussions and attempts around internalization before, all with react-intl
. You can find them here, here and here.
They seemed a little out of date, and little bit more complex than what I needed, so I built a proof-of-concept myself with react-universally
as of today. You can find it here.
The major difference is that the prior attempts had support for multiple languages, including language toggling (it did have bugs though). My branch above essentially sets up react-intl v2
with extraction of messages so that in the future I can add support for more languages as I reach that usecase. The TODOs for those can be found here incase anyone else needs the feature and wants to help.
Hope this helps!
Hi folks! I am curious if anyone has a fork/branch with a sample
i18n
implementation? Also, is there interest in making it part ofreact-universally
as a best practice?