Rule no-translation-key-interpolation requires serviceName
edcheung1 opened this issue · comments
Ed Cheung commented
The rule no-translation-key-interpolation
checks for the following syntax to flag interpolated strings as translation keys:
<serviceName>.t(`some interpolated string`)
We currently import our translation method directly (i.e. import { t } from 'i18n'
) as opposed to importing the library (i.e. import i18n from 'i18n'
). The rule is not able to catch translation key interpolations in this format:
t(`some interpolated string`)
Possible fix:
- Add additional check for
isT(node)
that doesn't check forserviceName