`Trans` context handled differently from `t` function about react-i18next HOT 10 CLOSED

should be addressed with v14.0.6

from react-i18next.

This test is green: https://github.com/i18next/react-i18next/blob/master/test/trans.render.spec.jsx#L880
Can you try to setup a failing test here?

from react-i18next.

wow, thank you for the fast response!

from react-i18next.

If you like this module don’t forget to star this repo. Make a tweet, share the word or have a look at our https://locize.com to support the devs of this project.

There are many ways to help this project 🙏

from react-i18next.

I just tried to update my reproduction to 14.0.6 but I still get a different output when I use the context property of Trans :(

https://stackblitz.com/edit/vitejs-vite-9ntmun?file=package.json&terminal=dev

from react-i18next.

ahh I know why....

from react-i18next.

That's because of the override of the prefix and suffix here: https://github.com/i18next/react-i18next/blob/master/src/TransWithoutContext.js#L357 but I don't remember why this was done like that... maybe @jamuhl remembers why?
Beside that, I can only say that normally the context interpolation for Trans component should by done with tags and children (<1></1>) and not like with the t function with {{context}}...

from react-i18next.

fyi: I locally just removed to pass the interpolationOverride object to... and all tests are still green... so it may be we can simplify that to no have the interpolation option override? @jamuhl ?

from react-i18next.

I just released v14.0.7 that removes the internal interpolationOverride handling...
if the community opens new issues because of that, we will probably revert this change

from react-i18next.

Seems to work now, thanks! :)

from react-i18next.