Passing namespace to withTranslation HOC doesn't work when using compose about babel-plugin-i18next-extract HOT 3 CLOSED

Composing is indeed not supported and I'm kind of on the fence about adding such feature. Sure we could support compose function from recompose, but then we would have to support flowRight from lodash, then compose from lodash FP and then custom implementations of compose and probably other very specific currying functions and so on. Even then, should we support both array and variadic version of lodash's flowRight?

Maybe we could try to be a little smart and just rely on a (possibly configurable) whitelist of compose keywords, still that sounds like a very specific use-case to me and a lot of "magic" would probably be involved to support every or even most use-cases.

I'm sure you know it, though as a workaround, you can use a comment hint for this:

// i18next-extract-mark-ns-start namespace1
const SomeComponent = ({ t }) => <div>{t('mykey')}</div>;
// i18next-extract-mark-ns-stop

export const SomeComponentWrapped = compose(withTranslation('namespace1'))(SomeCompone

That was one of the main intentions behind comment hints by the way. Avoid blocking the user because a specific case (typically something very "runtime-ish") isn't or won't be supported by the library.

If you have any strong opinion on this, I'd be glad to hear it.

from babel-plugin-i18next-extract.

Interesting, that makes sense.

It would be nice to be able to pass an option to the config that says everything in x directory should have y namespace instead of declaring that inside each file, but I think that would require changing the i18next API as well.

from babel-plugin-i18next-extract.

This would really help us :)

from babel-plugin-i18next-extract.