Context.t not being passed on server-side (isomorphic) render about redux-i18n

[shankie-codes]

Ah, of course, it's always (not always, but a lot of the time!) the case that as soon as you post an issue, you work out a solution.

In the example above, the <I18n> wrapper was quite high in the stack, just below my <Provider>. But, in between that and the content that actually needs translating, I have React Router v3 routes and a Material UI <MuiThemeProvider/>. At any rate, moving it down my tree seems to have solved it.

I'd happily like to hear though if anyone has any theories on why this might not pass context through other wrapper components on the server side!

Closing for now...

[mrchief]

I'm using React Router 4 and it needs to be higher than the router. Otherwise I get t as undefined. :)

[shankie-codes]

I've also found that, in some situations where context.t isn't working, the HOC approach works fine