Support different looking Trans props

[grydstedt]

For parsing the Trans key there are multiple valid ways of doing props:

<Trans i18nKey="key" />
<Trans i18nKey='key' />
<Trans i18nKey={"key"} />
<Trans i18nKey={'key'} />

Could we add those to the regex?

[cheton]

Sure! I will check how to fine tune this part:

const reTrans = new RegExp('<Trans([^]*?)>([^]*?)</\\s*Trans\\s*>', 'gim');
const reTransKey = new RegExp('[^]*i18nKey="([^"]+)"[^]*', 'im');

[grydstedt]

Awesome! while we're on that another great thing would be the ability to have custom component names and key prop name. We, for example, have a wrapper component that looks like this:

<I18N __t="key" />

It would be great if I could use custom names in that regex for Trans and i18nKey

[wichert]

FWIW I just submitted PR #71 which changes that code a bit and might make this easier.

[cheton]

v2.3.1 added context and count options for Trans
https://github.com/i18next/i18next-scanner/releases/tag/v2.3.1

v2.4.0 added support for using different component name and i18nKey prop:
https://github.com/i18next/i18next-scanner/releases/tag/v2.4.0

trans: {
    component: 'Trans',
    i18nKey: 'i18nKey',
    extensions: ['.js', '.jsx'],
    fallbackKey: true
}

[grydstedt]

You rock!